[#506] Update contributing guidelines to reflect latest assumptions #524
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #506.
This pull request aims to update the project's contributing guidelines to reflect recent changes in the development workflow. The modifications include moving the ticket to the 'in review' status when the PR is ready for review, transitioning the PR from draft to an actual PR, addressing all change requests before merging into the
develop
branch, and automating the deployment process to the test and staging environments. These updates are intended to enhance the management of tickets, PRs, and branches, streamlining the development process and ensuring more efficient handling during the development and review phases.The changes in this pull request involve updating the CONTRIBUTING.md document to incorporate the latest development workflow practices. The recommendation is made against using rebase and merge, suggesting the use of proper merges for easier feature cherry-picking. Additionally, details are added to explain the benefits of proper merges over rebase and merge, clarifying how they facilitate cherry-picking features. A new section is introduced to explain the purpose and usage of an "In Review" column. These adjustments ensure that contributors are informed about the updated guidelines effectively, enhancing the overall development process and collaboration within the project.