QuantEcon / QuantEcon/action-style-guide
ENH: PR comment information (overly descriptive)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 27m
- Merged PRs (30d)
- 1
Description
The PR comment output is currently over detailed and we can adjust it
- no need to comment on any rules that are found to be in compliance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the code that assembles the pull request comment output; the issue does not name a file or test. The change is complete when rules found to be in compliance are omitted from the comment while other output remains available for review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100