Searched full:commits (Results 1 – 25 of 40) sorted by relevance
12
| /Zephyr-latest/ |
| 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-latest/scripts/checkpatch/ |
| D | maintainer-checkpatch.bash | 12 # usage: maintainer-checkpatch.bash [(-n <num commits>) | (-c <commit>)] [-s]
13 # where: -n <num commits> selects the last n commits (default: 1)
40 printf "usage: %s [(-n <num commits>) | (-c <commit>)] [-s]\n" $exe_name >&2
|
| D | check_known_checkpatch_issues.sh | 13 # where: -u updates the known_checkpatch_issues db and commits it
|
| /Zephyr-latest/scripts/ci/ |
| D | guideline_check.py | 41 description="Check commits against Cocccinelle rules", allow_abbrev=False)
44 parser.add_argument('-c', '--commits', default=None,
53 if not args.commits:
68 commit = sh.git("diff", args.commits, **sh_special_args)
|
| D | test_plan.py | 161 if 'west.yml' in self.modified_files and args.commits is not None:
164 old_manifest_content = repo_to_scan.git.show(f"{args.commits[:-2]}:west.yml")
405 parser.add_argument('-c', '--commits', default=None,
461 if args.commits:
462 commit = repo_to_scan.git.diff("--name-only", args.commits)
|
| D | version_mgr.py | 39 help="List weekly commits")
|
| /Zephyr-latest/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-latest/scripts/ |
| D | get_maintainer.py | 7 Lists maintainers for files or commits. Similar in function to
81 "commits",
84 "commits",
234 def commits2areas(self, commits): argument
237 are modified by the commit range in 'commits'. 'commits' could be e.g.
241 # Final '--' is to make sure 'commits' is interpreted as a commit range
243 for path in _git("diff", "--name-only", commits, "--").splitlines():
276 # 'commits' subcommand implementation
278 commits = args.commits or ("HEAD~..",)
279 _print_areas({area for commit_range in commits
|
| D | series-push-hook.sh | 25 # At each (forced) push, examine all commits since $remote/main
|
| /Zephyr-latest/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
|
| /Zephyr-latest/doc/contribute/ |
| D | contributor_expectations.rst | 24 commits and any combination of smaller PRs for testing and preview purposes.
54 Multiple Commits on a Single PR
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
357 address you use to sign your commits. If they don't match, the CI system will
360 If you intend to edit commits using the Github.com UI, ensure that your github profile
378 Changes are submitted as Git commits. Each commit has a *commit
435 ``FILE`` is a file you are changing, and using previous commits that
468 `changelog <https://github.com/zephyrproject-rtos/zephyr/commits/main>`__.
857 .. note:: As more commits are merged upstream, the GitHub PR page will show
860 as the commits will be rebased as part of merging anyway, and triggering
[all …]
|
| /Zephyr-latest/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
|
| /Zephyr-latest/.github/workflows/ |
| D | manifest.yml | 35 check-impostor-commits: 'true'
|
| D | compliance.yml | 33 # Ensure there's no merge commits in the PR
35 (echo "::error ::Merge commits not allowed, rebase instead";false)
|
| D | greet_first_time_contributor.yml | 39 and update (by amending and force-pushing the commits) your pull request if necessary.
|
| /Zephyr-latest/scripts/ci/stats/ |
| D | merged_prs.py | 123 prj['commits'] = pr.commits
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 127 provided. All commits shall be related to a bug report or change
128 request in the issue tracker. Commits without a valid reference
195 vulnerability reporting channel (if there is one), can accept commits
|
| /Zephyr-latest/scripts/release/ |
| D | list_devicetree_bindings_changes.py | 42 binding between the start and end commits. See subclasses
52 start and end commits.'''
505 bindings between two commits, in .rst format suitable for copy/pasting
|
| /Zephyr-latest/subsys/testsuite/coverage/ |
| D | coverage.h | 47 * Following GCC commits introduced these changes:
|
| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 87 * Avoid creating large commits that contain both trivial and non-trivial changes.
|
12
