Miserlou / Miserlou/WhitespaceBot
Watch out for negative karma
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 78
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
"This is possibly the most pointless proposed commit of all time." https://github.com/danchoi/vmail/pull/61
"I have wondered how long it would take until the invention of @github SPAM! BE GONE!" https://github.com/robbyrussell/oh-my-zsh/pull/882
The bot seems to create pull requests that smush together lots of unrelated commits, e.g. https://github.com/technomancy/emacs-starter-kit/pull/125
Before I contribute to projects, I often need to do a cleanup (mixed tabs/spaces, inconsistent indentation, whitespace-only lines, mixed unix/dos format). This would be more valuable than twiddling trailing whitespace, which is likely to just add commit noise. But it would be harder to do safely automatically.
This should be strictly opt-in and configurable for project style, your current MO will get you labeled spammy.
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 files, tests, or entry points are named. Start by surveying the repository to find how pull requests and whitespace changes are generated, then determine how opt-in project style configuration and safe cleanup could fit. Done would require avoiding unrelated commits and making the proposed behavior explicitly configurable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100