Document branches management for maintainers
Open
Nobody has claimed this yet.
question
- Dominant language
- Scala
- Stars
- 136
- Forks
- 555
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 4
Description
Need to document how we manage branches on PrestaShop
devversusmaster(for modules)1.7.x.ybranches versusdevelop(for Core)
Why we use rebase instead of merge, how we merge 1.7.x.y into develop ...
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 file or documentation entry point is named. Locate the existing maintainer or developer documentation, then compare it with the branch workflows listed here: module branches, Core release branches, develop, rebasing, and merging release branches. Done means these practices and their rationale are documented clearly for maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100