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
- [javascript] about source control
- linux - about version control by git (remote ⇔ remote)
- apache - about handshake error due to tls version
- [about java map/{}] the source code image does not come out
- about installing 32-bit version of mysql on 64-bit pc
- about linux python version change
- javascript - about microsoft edge latest version 83
- i want to control the relay destination for each source ip address with postfix
- question about source enumerating urls for ie launched in c++
- about error control operator (@ added to expression) (php)
- javascript - server control: about radio button list
- access - about tab control text boxes
- firebase - flutter: about changing the version of packages such as flutterfire
- c # - about xcode version
- version control - i can't update the firebase cli
- android - about the sdk version to install
- github - is it possible to fork to different version control hosting services for other people's projects?
- about java version
- c # - about wpf x button control
- about os version upgrade support in ios apps
Trends
- php - coincheck api authentication doesn't work
- php - i would like to introduce the coincheck api so that i can make payments with bitcoin on my ec site
- [php] i want to get account information using coincheck api
- python - you may need to restart the kernel to use updated packages error
- python 3x - typeerror: 'method' object is not subscriptable
- the emulator process for avd pixel_2_api_29 was killed occurred when the android studio emulator was started, so i would like to
- javascript - how to check if an element exists in puppeteer
- xcode - pod install [!] no `podfile 'found in the project directory
- vuejs - [vuetify] unable to locate target [data-app] i want to unit test to avoid warning
- android studio - unresolved reference comes out in kotlin
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".