[#434] Implement new Git Workflow proposal in project #673
+68
−101
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…osal The commit modifies the CONTRIBUTING.md file to reflect the changes introduced by the new Git workflow proposal[^1]. Specifically, it updates the documentation to align with the revised branching structure, deployment process, environments, workflow steps, and roles and responsibilities detailed in the proposal. These changes aim to ensure that contributors understand and adhere to the new workflow guidelines established for the project. [^1]: #289
5 tasks
The commit removes the manual deployment process as part of the old Git workflow. The changes involve updating the `build-and-deploy-dev.yml` github workflow by eliminating the manual deployment instructions and optimizing the deployment configuration. The obsolete deployment script, `deploy-dev-from-tag.yml`, is deleted. These modifications align with the new streamlined Git workflow proposal, aiming to enhance efficiency and accuracy in the project's release process.
The commit adjusts the `.github/workflows/build-and-deploy-test.yml` file to restrict the triggering of test deployments solely by specific tags within the repository. The modifications include altering the workflow to activate upon tag creation events that match the specified criteria, safeguarding that deployments to the test server are solely initiated by tag creation events. This change reinforces adherence to the new Git workflow proposal, guaranteeing that deployments to the test environment occur efficiently and accurately by aligning with the revised deployment process.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #434.
The changes introduced in this pull request aim to enhance the project's Git workflow by aligning it with a new proposal. The primary goal is to simplify the release candidate pull request process and minimize potential errors by implementing a new Git workflow. The first commit ensures that deployments to the test server are triggered only by specific tags, enforcing the revised deployment process outlined in the new workflow proposal. The second commit removes the obsolete manual deployment process from the old Git workflow, aligning with the updated deployment mechanisms suggested in the new proposal. By adhering to the new Git workflow proposal, the project aims to improve efficiency and accuracy in its release processes.