Editing
Git Workflow Best Practices for Elixir Development
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Branching Strategy === Developers should follow a branching strategy that promotes isolation of features and bug fixes, and allows for easy collaboration and code review. A popular branching strategy for Elixir development is the Gitflow Workflow: 1. **Master Branch**: Represents the production-ready codebase. 2. **Develop Branch**: Serves as the main branch for ongoing development. 3. **Feature Branches**: Created for new features and should be based on the Develop branch. 4. **Release Branches**: Created for preparing releases and should be based on the Develop branch. 5. **Hotfix Branches**: Created for addressing critical issues in the production code and should be based on the Master branch.
Summary:
Please note that all contributions to Elixir Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Elixir Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information