cloudpups / cloudpups/github-teams-user-sync
Enhance logging
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
For my own sanity, the bot must output additional details when performing operations. For example,
* Any time the bot is trying to add a user to the team, if the user doesn't exist and/or is "dormant" the sync bot must clearly state so. At this point in time, the bot does output users with Issues... However, additional clarity could be had by clearing separating/categorizing what "type" of issues are found with the user. More thoughts are needed on this.
* If an Org has not granted the app the proper permissions, some operations will fail. The logs must clearly call attention to the fact that the bot does not have permissions, and that folks must poke the Org Owners to update said permissions (by requesting the updated permissions request from the bot).
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 tracing the bot's team-sync operations and existing logging, since no files or tests are identified in the issue. The work is done when logs clearly distinguish nonexistent or dormant users, categorize user issues, and call attention to insufficient organization permissions with the requested next step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100