[ENHANCEMENTS]: codeowners, teams for timed
Open
Nobody has claimed this yet.
enhancement
quality
- Dominant language
- JavaScript
- Stars
- 19
- Forks
- 12
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 8
Description
Should we use dev-timed for all changes in this repo? Or maybe split it in dev-timed-frontend and dev-timed-backend?
That would make sense, for now this only fixes "unwanted" mails for @adfinis/dev-frontend
Originally posted by @c0rydoras in https://github.com/adfinis/timed/issues/171#issuecomment-2112012560
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
Review the repository's current CODEOWNERS configuration and GitHub team ownership setup, focusing on the proposed dev-timed and @adfinis/dev-frontend ownership. Decide whether one team or separate frontend and backend teams should receive change notifications, and consider the work done when the chosen ownership rules prevent unwanted mails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100