Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update rule descriptions for landmark rules #1184

Merged
merged 2 commits into from
Oct 11, 2018

Conversation

jeeyyy
Copy link
Contributor

@jeeyyy jeeyyy commented Oct 10, 2018

A previously closed PR - #1156, did not run build to update the rule descriptions. This is a chore to update the rule descriptions.

Closes issue: NA

Reviewer checks

Required fields, to be filled out by PR reviewer(s)

  • Follows the commit message policy, appropriate for next version
  • Has documentation updated, a DU ticket, or requires no documentation change
  • Includes new tests, or was unnecessary
  • Code is reviewed for security by: @WilcoFiers

@jeeyyy jeeyyy requested a review from a team as a code owner October 10, 2018 13:03
@jeeyyy jeeyyy merged commit f98b830 into develop Oct 11, 2018
@jeeyyy jeeyyy deleted the fix-rule-descriptions branch October 11, 2018 10:52
Danidude pushed a commit to tingtun/axe-core that referenced this pull request Nov 1, 2018
WilcoFiers pushed a commit that referenced this pull request Nov 20, 2018
**Short Description:**
Preventing us to open PR's like this - #1184

**Long Description:**
There has been several PR's in the past, where changes are done, but the `rule-descriptions` are not updated, because `build` was not run as a part of the development efforts.

These usually happen when the metadata of a rule spec or check spec is changed. 

Overhead being unrelated changes show up on other work.

This PR adds `grunt configure`, which builds `doc/rule-descriptions.md` as a part of pre-commit hook. This should alleviate the above 

Closes issue: NA

## Reviewer checks

**Required fields, to be filled out by PR reviewer(s)**
- [x] Follows the commit message policy, appropriate for next version
- [x] Has documentation updated, a DU ticket, or requires no documentation change
- [x] Includes new tests, or was unnecessary
- [x] Code is reviewed for security by: @WilcoFiers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants