Searched refs:commits (Results 1 – 25 of 29) sorted by relevance
12
| /Zephyr-Core-3.7.0/ |
| D | .gitlint | 7 # By default gitlint will ignore merge commits. Set to 'false' to disable.
8 ignore-merge-commits=false
9 ignore-revert-commits=false
10 ignore-fixup-commits=false
11 ignore-squash-commits=false
52 # Whether to ignore this rule on merge commits (which typically only have a title)
54 ignore-merge-commits=false
|
| D | CONTRIBUTING.rst | 22 contributions, and documented with a ``Signed-off-by`` line in commits.
|
| D | CODE_OF_CONDUCT.md | 47 comments, commits, code, wiki edits, issues, and other contributions that are
|
| /Zephyr-Core-3.7.0/scripts/ci/ |
| D | guideline_check.py | 46 if not args.commits:
61 commit = sh.git("diff", args.commits, **sh_special_args)
|
| D | test_plan.py | 152 if 'west.yml' in self.modified_files and args.commits is not None:
450 if args.commits:
451 commit = repo_to_scan.git.diff("--name-only", args.commits)
|
| D | check_compliance.py | 1585 COMMIT_RANGE = args.commits
|
| /Zephyr-Core-3.7.0/doc/services/device_mgmt/ |
| D | mcumgr_backporting.rst | 54 * The SHAs of the commits, if the PR has already been merged
66 Backporting a fix means that some or all of the fix commits, as they exist in the current version,
74 1. Port the fix commits from the current version to the previous version.
75 Even if some of the commits require changes, keep the commit messages of all the ported commits
76 as close to the ones in the original commits as possible, adding the following line:
|
| /Zephyr-Core-3.7.0/scripts/ |
| D | get_maintainer.py | 234 def commits2areas(self, commits): argument
243 for path in _git("diff", "--name-only", commits, "--").splitlines():
278 commits = args.commits or ("HEAD~..",)
279 _print_areas({area for commit_range in commits
|
| D | set_assignees.py | 77 if pr.commits == 1 and (pr.additions <= 1 and pr.deletions <= 1):
|
| D | checkpatch.pl | 1035 my @commits = ();
1051 unshift(@commits, $sha1);
1055 die "$P: no git commits after extraction!\n" if (@commits == 0);
1056 @ARGV = @commits;
|
| /Zephyr-Core-3.7.0/doc/develop/west/ |
| D | built-in.rst | 141 However, if you had added some local commits onto a previously detached
143 behind some commits which are no longer referred to by any branch. These
145 this if you have local commits in the project, make sure you have a local
152 long as they point to commits that are descendants of the new
158 between your branch and new commits brought in by the manifest. You
164 because it does not try to hold on to your commits and simply
170 - in projects where your branch diverged from the incoming commits, it
|
| D | manifest.rst | 32 The history of the manifest repository is the line of Git commits which is
33 "floating" on top of the gray plane. Parent commits point to child commits
39 The commits in the manifest repository (again, for upstream Zephyr this is the
41 commit specifies the corresponding commits which it expects in each of the
49 commits ``D`` and ``E``) and removed (``P2`` between the same
50 manifest repository commits)
63 - Project repository commits can be "skipped": ``P3`` moves forward
64 multiple commits in its history from ``B → C``.
280 in the cloned repository limited to the given number of commits. This
311 HEAD, and commits not available locally, but will not fetch commits if
|
| D | workspaces.rst | 24 to check it out or otherwise modify it yourself. For instance, any commits
|
| /Zephyr-Core-3.7.0/doc/project/ |
| D | modifying_contributions.rst | 12 of the pull requests are responsible for amending their original commits
19 * a developer cherry-picks commits submitted by other contributors into their
|
| D | issues.rst | 7 issues, it is recommended to cross-reference source code commits with the
|
| D | release_process.rst | 395 - Has a dedicated maintainer who commits to respond to issues / review patches.
|
| /Zephyr-Core-3.7.0/doc/contribute/ |
| D | contributor_expectations.rst | 24 commits and any combination of smaller PRs for testing and preview purposes.
57 Contributors are further encouraged to break up PRs into multiple commits. Keep
62 the PR into multiple commits targeting these specific changes:
107 - When breaking a PR into multiple commits, each commit must build cleanly. The
293 - Reviewing commits separately when the requested changes cascade into the
294 later commits.
|
| D | guidelines.rst | 141 For your commits, replace:
150 ``git commit -s``. Use other commits in the zephyr git history as examples.
174 * the cherry-picked commits or portions of a commit shall preserve the original
369 Changes are submitted as Git commits. Each commit has a *commit
426 ``FILE`` is a file you are changing, and using previous commits that
459 `changelog <https://github.com/zephyrproject-rtos/zephyr/commits/main>`__.
849 .. note:: As more commits are merged upstream, the GitHub PR page will show
852 as the commits will be rebased as part of merging anyway, and triggering
899 .. note:: While amending commits and force pushing is a common review model
903 one - GitHub complains it can't find older commits. You're also not
[all …]
|
| /Zephyr-Core-3.7.0/scripts/ci/stats/ |
| D | merged_prs.py | 123 prj['commits'] = pr.commits
|
| /Zephyr-Core-3.7.0/doc/safety/ |
| D | safety_requirements.rst | 87 * Avoid creating large commits that contain both trivial and non-trivial changes.
|
| /Zephyr-Core-3.7.0/doc/kernel/data_structures/ |
| D | mpsc_pbuf.rst | 12 producer fills the data and commits it. Consuming a packet is also performed in
|
| /Zephyr-Core-3.7.0/doc/security/ |
| D | secure-coding.rst | 127 provided. All commits shall be related to a bug report or change
195 vulnerability reporting channel (if there is one), can accept commits
|
| D | vulnerabilities.rst | 424 …<https://github.com/zephyrproject-rtos/zephyr/pull/23821/commits/11b7a37d9a0b438270421b224221d9192…
615 …<https://github.com/zephyrproject-rtos/zephyr/pull/23821/commits/0b39cbf3c01d7feec9d0dd7cc7e0e374b…
636 …<https://github.com/zephyrproject-rtos/zephyr/pull/23821/commits/989c4713ba429aa5105fe476b4d629718…
|
| /Zephyr-Core-3.7.0/doc/releases/ |
| D | release-notes-1.5.rst | 235 * ``ZEP-565`` - Ethernet/IPv4/TCP: last commits are breaking network support
|
| /Zephyr-Core-3.7.0/doc/develop/ |
| D | modules.rst | 128 commits, tags, etc. are always preserved). This policy also allows to run
169 downside of this approach is that two additional merge commits are generated in
|
12
