1
The company I work for hires some interns who take care of tasks small of various languages and different parts of the program (in order to enable them), but recently one of our interns made some commits from one branch into another in our remote repository, in order not to exclude the branch, recreate it and make the changes in some commits to make up this, I wonder if there is any method of:
- "Rewrite" the commits, ignoring those who has no branch nexus, remaking the remote branch history.
- Save commit changes to the wrong branch so that in the future they are placed in the right branch
- Keep history with changes in date and time
I’m working with Bitbucket and Tortoisegit.
I think it’s worth putting an addendum to deadly commits, like sending the bank password unintentionally in the file
– Jefferson Quesado
The question talked about keeping the history and keeping the changes, it does not seem to be the case. The only really safe thing to do when sending the password from the GIT database is to change the password of the database.
– Ricardo Moraleida
Well, that’s true, but sometimes we fool around and need to rewrite history. I know this is beyond what was asked by @Paz, but it’s something I always find important to quote, by neurosis even. Github has a post on this subject
– Jefferson Quesado