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.
DOCS: Stop requiring every commit to reference an issue
See original GitHub issue@jbrockmendel mentioned in #4885 that this requirement is painful. @vnlitvinov asked here whether we should keep the requirement.
Similar projects pandas, vaex, dask, and polars do not seem to have this requirement.
I vote for relaxing this requirement but still requiring commits to start with one of an allowed set of prefixes, currently {"FEAT", "DOCS", "FIX", "REFACTOR", "TEST", "PERF"}. The contributing guidelines should say that if the PR fixes an existing relevant issue, the commit message should include that issue’s number.
@modin-project/modin-contributors @modin-project/modin-core please share your thoughts.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 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
What I would like to actually do is to keep the same logic we were doing as regular contributors (i.e. creating issues for tracking purposes etc), but do not require these issues to be created by external contributors.
In my opinion, accepting some random external contribution should be as frictionless as possible.
I agree with @vnlitvinov - that way we don’t have to have a complicated set of rules for whose commits are formatted in a specific way for which people, but our commits (on master) are still nicely formatted!