While we have team to maintain same project and (some times) same file, we use git commit to track feature by feature(or update by update) refinements/updates. Each commit will pass to testing team for testing(usually testing in sandbox before deployment/release to Production),
- There are chances of deploy multiple commits, after testing and confirm
- There can be few days or weeks after the commit been deploy/release to Production.
-- At that time, we might already forget where and when the last update has been made(even sometimes the feature/refinement has been forgotten), where is the last production version/status
- So here comes the challenge:
How to use Git branch to maintain the tesing commit to released PRD status?
Is there any comment or tag to show the status of the deployment to PRD
or the deployment note?
Use Tag?
The light way, fast way to do this can be git tag, we can create a simple tag AT deployment date/process.
By doing that, we track the last deployment commit/point; so we knows where is the status in Production, and the lasttest commit(s) in the branch log. Each to refresh the memory on what updates has been made in sandbox(i.e.)
Detail operation, we can reference on the git tag usage, I.e. this article https://www.codenong.com/cs106325649/
How to given more note/description for Deployment Notes/Steps(some times it related with new custom objects), git tag has the comment paramter, the other way is to keep the deployment note in the commit message.
The other ways is using Branch to track the production status, but that will consume more times between deployment process, we can choose this option in same cases, depends on the project situation.
.png)