You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes. TBD:
Currently, developers can inadvertently merge TODO comments into the production main branch. These TODO comments are useful during development but should not be present in the production code.
Describe the solution you'd like
We need a GitHub (later also GitLab) Action that allows TODO comments in the development branches but issues a warning or fails the build if TODO comments are present when merging into the production main branch.
Describe alternatives you've considered
No response
Additional context
We are specifically targeting our TODO convention, not others by default.
And we suggest converting these into GitHub Issues or Jira Tasks using the information from the metadata.
I have checked existing list of Feature requests and the Contribution Guide
I confirm I have checked existing list of Feature requests and Contribution Guide.
The text was updated successfully, but these errors were encountered:
Related area
Actions, Convention, CI/CD
Is your feature request related to a problem?
Yes. TBD:
Currently, developers can inadvertently merge TODO comments into the production main branch. These TODO comments are useful during development but should not be present in the production code.
Describe the solution you'd like
We need a GitHub (later also GitLab) Action that allows TODO comments in the development branches but issues a warning or fails the build if TODO comments are present when merging into the production main branch.
Describe alternatives you've considered
No response
Additional context
We are specifically targeting our TODO convention, not others by default.
And we suggest converting these into GitHub Issues or Jira Tasks using the information from the metadata.
I have checked existing list of Feature requests and the Contribution Guide
The text was updated successfully, but these errors were encountered: