JSDoc Integration #223
Closed
BenLloydPearson
announced in
Automation Example Bounties
Replies: 1 comment
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Enforce JSDoc Requirements for New Classes
Automation Name: review_new_class_jsdoc
Require JSDoc for all new JavaScript classes.
Conditions (all must be true):
{{ is.javascript and is.new | some }}
\/\*\*([\s\S]*?)\*\/
Automation Actions:
⚠️ Missing JSDoc
label.Assign JSDoc Reviewer
Automation Name: assign_jsdoc_only
Assign reviewers for PRs that only contain changes to JSDoc.
Conditions (all must be true):
\/\*\*([\s\S]*?)\*\/
Automation Actions:
ORG/tech-writers
team.📓 JSDoc Only
labelReview JSDoc Input Parameters
Automation Name: review_jsdoc_input
Warn PR authors when they change JavaScript function or constructor input parameters without updating JSDoc content./
Conditions (all must be true):
/(?:function\s*[^(\n]*\(|\([^()]*\)\s*=>|function\s*[^(\n]*\{|[^:\n]*:\s*function\s*\()([^)]*)\)/g
constructor\s*\(([^)]*)\)
\* @param
Automation Actions:
Note: This example may not trigger for 100% of input parameter changes, so validate the regex used in this example against your organization's requirements.
Review JSDoc for Large Changes
Automation Name: review_jsdoc_large
Require more extensive reviews for large JavaScript changes that lack JSDoc updates.
Conditions (all must be true):
Automation Actions:
ORG/tech-writers
team.⚠️ Missing JSDoc
LabelAdditional Resources
Here are some additional examples you should incorporate into these automations:
Beta Was this translation helpful? Give feedback.
All reactions