Skip to content

Conversation

AquariusStar
Copy link
Contributor

Changing the wording of terms and correction of minor errors

P.S. I hope there are no more commits from d670089, 85b07bd, 9041f63 and 80b73e6. I don't have enough experience working with Git.

@love-linger
Copy link
Collaborator

Hi, @AquariusStar

You can avoid introducing merged commits by following these steps:

  1. Add a new remote in your forked repo that points to this repo https://github.com/sourcegit-scm/sourcegit.git, and give it a friend name, for example: official
  2. Fetch the latest commits of remote official
  3. Create a new branch that based on the latest remote branch official/develop, and give it a meaningful name, for example: feature/enhance_russian_translation
  4. Cherry-pick the newer commits you want to merged into the official repo one-by-one.
  5. Push the create branch to your github original repo.
  6. The you can create a PR from github website with the branch you have just pushed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants