SSWConsulting / SSWConsulting/SSW.Rules
🔍 Investigate GitHub Actions Bot Contributions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
CC @adamcogan @bradystroud
Hi Team,
Description
The GitHub actions bot is making a lot of commits in the contributions graph for SSW.Rules.Content. This may be from one of the PR linter actions. We need to assess whether these commits are valuable, and if not, consider turning off the bot. Additionally, let's link to a rule about markdown linting content PRs in the newsletter.
Acceptance Criteria
- Investigate the commits made by the GitHub actions bot on SSW.Rules.Content.
- Determine if the commits are valuable or redundant.
- If the commits are not valuable, consider disabling the bot or adjusting its configuration.
- Update the newsletter to include a link to a rule about markdown linting content PRs.
Figure: Finally, Tiago has some competition 🥊
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named. Start by reviewing the GitHub Actions bot commits and PR linter actions in SSW.Rules.Content, then assess whether the commits are valuable or redundant. Done means documenting that assessment, adjusting or disabling the bot if needed, and adding the markdown-linting rule link to the newsletter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, markdown
- Domain
- ci-cd, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100