MatteoGabriele / MatteoGabriele/agentscan-action
re: known-bots.ts (drive-by knowledge sharing)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 59
- Forks
- 5
- Avg merge
- 12h 33m
- Merged PRs (30d)
- 1
Description
FYI: GH API's user object has a user type that can tell you if a thing is a GH App or not — there's no need to check if the login ends in a [bot].
I discovered this when making a GH app back in the day and was also trying to make it configurable to let people exclude bot accounts: https://github.com/sanitizers/chronographer-github-app/blob/da991e08256a17ef0d013ecc6ed0908051e97c54/chronographer/event_handlers.py#L440C29-L440C29.
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
Start by reading known-bots.ts and trace where GitHub user objects are classified as bots. Compare the current login-suffix check with the GitHub API user type described in the issue and identify the existing checks that would need updating; done means bot detection no longer depends on a login ending in [bot].
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions, typescript
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100