ishangsf/rspec
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

RULEAPI-660: Add an exception to the new-rule workflow (#133)

Browse Source
This commit is contained in:
Arseniy Zaostrovnykh 2021-06-16 15:59:09 +02:00 committed by GitHub
parent a37ee26e57
commit cf4373c8e8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.adoc
View File

@ -46,7 +46,7 @@ Thus every newly created rule or modification of rule should follow these steps:
. Ask for a review . Ask for a review
. Create an implementation ticket . Create an implementation ticket
. Implement the new rule or the change in the existing rule . Implement the new rule or the change in the existing rule
. Merge the RSPEC PR as soon as the implementation is ready . Merge the RSPEC PR as soon as the implementation is ready (unless the implementation needs access to the RSPEC before it is ready, see RULEAPI-660).
* Here "ready" means it is tested/validated/tuned/discussed and lacks only the rule metadata to be merged into analyzer's main branch. * Here "ready" means it is tested/validated/tuned/discussed and lacks only the rule metadata to be merged into analyzer's main branch.
. Fetch the updated metadata with `rule-api` . Fetch the updated metadata with `rule-api`
. Merge the implementation PR . Merge the implementation PR