jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 11:54:18 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #51921 from github/repo-sync

Browse Source 
Repo sync
This commit is contained in:
docs-bot
2024-08-05 17:40:23 -07:00
committed by GitHub
parent 10eec5033b c3444d02ce
commit 904b7f2eee
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
View File

@@ -366,7 +366,9 @@ updates:
### `commit-message` ### `commit-message`
By default, {% data variables.product.prodname_dependabot %} attempts to detect your commit message preferences and use similar patterns. Use the `commit-message` option to specify your preferences explicitly. By default, {% data variables.product.prodname_dependabot %} attempts to detect your commit message preferences and use similar patterns. Use the `commit-message` option to specify your preferences explicitly. This setting also impacts PR titles.
PR titles are always populated based on the commit messages, explicitly set or auto-detected from the repo history.
Supported options Supported options
@@ -376,7 +378,7 @@ Supported options
{% endnote %} {% endnote %}
* `prefix` specifies a prefix for all commit messages. * `prefix` specifies a prefix for all commit messages and it will also be added to the start of the PR title.
When you specify a prefix for commit messages, {% data variables.product.prodname_dotcom %} will automatically add a colon between the defined prefix and the commit message provided the defined prefix ends with a letter, number, closing parenthesis, or closing bracket. This means that, for example, if you end the prefix with a whitespace, there will be no colon added between the prefix and the commit message. When you specify a prefix for commit messages, {% data variables.product.prodname_dotcom %} will automatically add a colon between the defined prefix and the commit message provided the defined prefix ends with a letter, number, closing parenthesis, or closing bracket. This means that, for example, if you end the prefix with a whitespace, there will be no colon added between the prefix and the commit message.
The code snippet below provides examples of both in the same configuration file. The code snippet below provides examples of both in the same configuration file.