Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Standardize PR naming convention using GitHub Action
See original GitHub issueWe’ve created [Guideline] Pulsar PR Naming Convention and many contributors in Pulsar community follow the rules, which is great!
And we want to research whether we can improve this workflow furthermore by standardizing PR naming convention using GitHub Action.
@RobertIndie and @nodece have provided some references, which might be the potential solutions:
- https://github.com/amannn/action-semantic-pull-request
- https://github.com/zeke/semantic-pull-requests
- https://github.com/apache/apisix/blob/master/.github/workflows/semantic.yml
Besides, to reduce manual work, @codelipenghui suggests that a PR can be labeled automatically based on [xxx][xxx] in a PR title.
Anyone would like to help implement this idea? Thanks!
Issue Analytics
- State:
- Created a year ago
- Comments:18 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I am -1 on this and #16836 until the “standard” has been moved into a PMC controlled resource. A google doc is NOT PMC controlled. I also ask if these changes have gone through the PIP process?
The change may require a dev doc for itself and I’m curious whether there’s a discussion on dev@ (or collect feedback from any other public channel) since it can significantly change developer experience.