
.deepsource.toml configuration file are executed. Any changes that are detected are then committed back to the same branch. Refer to the respective’s language’s section for details on the code formatters that are available for each language and it’s .deepsource.toml configuration.
In cases where changes are made directly to the default branch without a pull request, a new pull request is automatically generated with the necessary formatting changes. This process ensures that any code changes made to the repository are consistently formatted and meet established standards, regardless of the method of modification.
GitHub imposes restrictions on creating commits on branches from other forks, which may occasionally prevent changes from being committed back. In such cases, we recommend merging the pull request as it is. Once the pull request is merged, DeepSource automatically identifies and incorporates the formatting transformations introduced in the merge commit.
.deepsource.toml file on the default branch, the entire codebase is formatted. However, subsequent to this initial formatting, only files that have been added or modified in a commit, pull request, or merge request are formatted.
It should be noted that for pull requests that have non-default branches as their base (such as pull requests to release branches), code formatting is not executed.