Searched refs:commits (Results 1 – 16 of 16) sorted by relevance
| /trusted-firmware-a/tools/conventional-changelog-tf-a/ |
| A D | index.js | 105 const generateTemplateData = function (sections, commits) { argument
109 sections: generateTemplateData(section.sections, commits),
110 commits: commits.filter(commit => section.scopes?.includes(commit.scope)),
116 if ((templateData.sections.length == 0) && (templateData.commits.length == 0)) {
127 sections: generateTemplateData(config.sections, commitGroup.commits),
128 commits: commitGroup.commits.filter(commit =>
|
| /trusted-firmware-a/tools/conventional-changelog-tf-a/templates/ |
| A D | commit-section.hbs | 4 {{#if commits.length ~}}
5 {{#each commits ~}}
|
| A D | template.hbs | 7 {{#each (tf-a-commits commitGroups) ~}}
|
| /trusted-firmware-a/docs/process/ |
| A D | faq.rst | 10 If you need to modify an existing patch set with multiple commits, refer to the
62 It is OK to create a patch based on commits that are only available in
64 that the dependency commits will change (for example due to patch set rework or
|
| A D | contributing.rst | 29 - Ensure commits adhere to the the project's :ref:`Commit Style`.
31 - Make commits of logical units. See these general `Git guidelines`_ for
34 - Keep the commits on topic. If you need to fix another bug or make another
41 some commits should be squashed together or addressed in a separate topic.
58 - For topics with multiple commits, you should make all documentation changes
|
| A D | commit-style.rst | 24 |TF-A| follows the `Conventional Commits`_ specification. All commits to the
88 While we don't enforce scopes strictly, we do ask that commits use these if they
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/process/ |
| A D | faq.rst.txt | 10 If you need to modify an existing patch set with multiple commits, refer to the
62 It is OK to create a patch based on commits that are only available in
64 that the dependency commits will change (for example due to patch set rework or
|
| A D | contributing.rst.txt | 29 - Ensure commits adhere to the the project's :ref:`Commit Style`.
31 - Make commits of logical units. See these general `Git guidelines`_ for
34 - Keep the commits on topic. If you need to fix another bug or make another
41 some commits should be squashed together or addressed in a separate topic.
58 - For topics with multiple commits, you should make all documentation changes
|
| A D | commit-style.rst.txt | 24 |TF-A| follows the `Conventional Commits`_ specification. All commits to the
88 While we don't enforce scopes strictly, we do ask that commits use these if they
|
| /trusted-firmware-a/docs/security_advisories/ |
| A D | security-advisory-tfv-5.rst | 51 whereas the EL3 was fixed in the later commits.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/security_advisories/ |
| A D | security-advisory-tfv-5.rst.txt | 51 whereas the EL3 was fixed in the later commits.
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | prerequisites.rst | 138 commits include a ``Change-Id`` footer, and this footer is typically
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | prerequisites.rst.txt | 138 commits include a ``Change-Id`` footer, and this footer is typically
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/ |
| A D | change-log.md.txt | 980 …- do not check merge commits ([77a0a7f](https://review.trustedfirmware.org/plugins/gitiles/TF-A/tr…
1191 - Added support for conventional commits through commitlint hook, commitizen
|
| /trusted-firmware-a/docs/ |
| A D | change-log.md | 980 …- do not check merge commits ([77a0a7f](https://review.trustedfirmware.org/plugins/gitiles/TF-A/tr…
1191 - Added support for conventional commits through commitlint hook, commitizen
|
| /trusted-firmware-a/docs/build/latex/ |
| A D | trustedfirmware-a.tex | 3094 commits include a \sphinxcode{\sphinxupquote{Change\sphinxhyphen{}Id}} footer, and this footer is t…
10769 While we don’t enforce scopes strictly, we do ask that commits use these if they
12166 Make commits of logical units. See these general \sphinxhref{http://git-scm.com/book/ch5-2.html}{Gi…
12171 Keep the commits on topic. If you need to fix another bug or make another
12182 some commits should be squashed together or addressed in a separate topic.
12213 For topics with multiple commits, you should make all documentation changes
12848 If you need to modify an existing patch set with multiple commits, refer to the
12920 It is OK to create a patch based on commits that are only available in
12922 that the dependency commits will change (for example due to patch set rework or
45199 whereas the EL3 was fixed in the later commits.
[all …]
|
Completed in 135 milliseconds