GitHub integration excessive commits

[ReenigneArcher]

The GitHub integration creates a new commit for every single changed file.

This can cause a lot of issues if repo maintainers are not careful.

1. It will trigger a workflow run for every commit on the PR. You need to enable workflow concurrency, but this could still lead to extra usage because the first workflows need to be cancelled after they are already started.
2. The merge gets really messy, unless the PR is squashed and merged (many people don’t even know what this is).
3. External services, such as SonarCloud, get confused and possibly rate limited

Suggestion:

• Put all changes into one file
• When there are new changes, and a PR is already open, rebase the PR branch and amend the commit instead of creating new ones

[Natalia]

Hi @ReenigneArcher , first of all, you are welcome to use Squash and merge option in the repository:

Then in Crowdin project > integration settings, you’re welcome to set the Sync schedule, so synchronization will happen after a set period of time:

GitHub Integration