Home>
Version management is done with SourceTree.
Normally, the feature branch is started from Git-flow, the revision commit, the new release is started, and the revision is committed (the version name is attached to the tag).
Here, I want to go back to the old version from the latest version and perform subsequent source control. How should I operate on SourceTree?
Example)
It is transitioned from Ver1.0 → Ver1.1 → Ver1.2 → Ver1.3 → Ver1.4, and I want to return all the Master branch and Develop branch to the state of Ver1.1 and perform subsequent management and development.
Normally, the feature branch is started from Git-flow, the revision commit, the new release is started, and the revision is committed (the version name is attached to the tag).
Here, I want to go back to the old version from the latest version and perform subsequent source control. How should I operate on SourceTree?
Example)
It is transitioned from Ver1.0 → Ver1.1 → Ver1.2 → Ver1.3 → Ver1.4, and I want to return all the Master branch and Develop branch to the state of Ver1.1 and perform subsequent management and development.
Even if you don't delete Ver1.2 or later
Return it in the form of Ver1.0->Ver1.1->Ver1.2->Ver1.3->Ver1.4->Ver1.1, and then you can manage from Git-flow.
-
Answer # 1
Related articles
- linux - about version control by git (remote ⇔ remote)
- [javascript] about source control
- version control - data not found in react + redux + typescript
- c # - about wpf x button control
- javascript - server control: about radio button list
- access - about tab control text boxes
- firebase - flutter: about changing the version of packages such as flutterfire
- [about java map/{}] the source code image does not come out
- version control - i can't update the firebase cli
- c # - about xcode version
- github - is it possible to fork to different version control hosting services for other people's projects?
- about java version
- php - about the version when developing using the framework
- about os version upgrade support in ios apps
- c # - about delivery of source code for systems using third-party components
- version control - the error "no plugin updates available" cannot be resolved (android studio version cannot be confirm
- about segment control of xcode
- mysql - about the rds engine version
- android - about the sdk version to install
- apache - about handshake error due to tls version
Trends
As a general rule, you should avoid the act of reverting the version as much as possible.
However, if you really want to revert to the original version, you can often do one of the following:
Usegit resetto return to the old version.Overwrite all files with older versions.
Create a new branch based on the old version and treat that branch as master.
If you have git pushed the wrong contents due to an operation mistake etc., I think that the method of "1" is fine, but if you want to treat it as the master based on the old version for some reason, "2" " I think that it is better to respond by one of the methods of "3".