SSWConsulting / SSWConsulting/SSW.Rules
👷 Choose and test feature branches management
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
Cc: @Freego1783 @Aibono1225 @babakamyljanovssw @isaaclombardssw @bradystroud
Hi team,
Pain
As per this comment here: https://github.com/SSWConsulting/SSW.Rules/issues/1463#issuecomment-2406374349
We need to find a proper way to manage long term feature branches.
Suggested Solution
I'm just copy/pasting the schema here:
Figure: Issac's schema about long terme feature branches management
Tasks
- Debate options
- Try on testings branches the 2 options
- write feedback
- Choose the best appropriate option
- Document the process
Thanks!
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 with the linked comment in issue #1463 and the schema image describing long-term feature branch management. Compare the two proposed options on testing branches, record feedback, and define the criteria for choosing one. Done means the team has selected an approach and documented the resulting process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100