atom feed rss feed
Renata's blog

Pushing a commit to a different repo

~ 2 min read

Photo taken from the top of a hill, overlooking light green ocean beaches

View from the Barra-Galheta beach trail, in Florianopolis, Brazil

My Outreachy internship with Debian is over. I'm still going to write an article about it, to let everyone know what I worked on towards the ending, but I simply didn't have the time yet to sit down and compile all the information.

As you might or might not have noticed, right after my last Outreachy activity, I sort of took a week off in the beach. \o/

Renata's picture, a white woman sitting on the grass, overlooking the beach below. She pets a brown stray that sits next to her

Mila, a cute stray dog that accompanied us during a whole trail

For the past weeks, I've also been involved in the organization of three events (one of them was a Debian Women meeting in Curitiba that took place two Saturdays ago and another one is Django Girls Porto Alegre, which starts tonight). Because of this last one, I was reviewing their Brazilian Portuguese tutorial and adding some small fixes to the language. After all, we are talking to women who read the tutorial during the workshop, so why all the mentions to programmers and hackers and such should mention the male counterpart in Portuguese? Women program, too!

When I was going to commit my fixes, though, I got an error:

remote: error: GH006: Protected branch update failed for refs/heads/master.
! [remote rejected]   master -> master (protected branch hook declined)


Yup, as it so happens more often than not, I forgot to fork the repository before starting to change the files! I just did 'git clone' straight to Django Girls' tutorial repository. But, since I had already done all the steps towards the commit, what could I do to avoid losing the changes? Could I just push this commit to another repository of my own and try and open a Pull Request to DjangoGirls/tutorial?

Of course I had to go and search for that. Isn't that what all programmers do? Go and find someone else who already had the same problem they have to try and find a solution?

Quick guide to the solution I've found:

[master 4d314550] Small fixes for pt-br version

The branch is: master

The id is: 4d314550

git push URL_FOR_THE_NEW_REPO commit_id:branch

Example with my repo:

git push 4d314550:master

And this was yet another article for future reference.

Related posts