• Home
  • Raw
  • Download

Lines Matching +full:commit +full:- +full:message +full:- +full:check

1 .. _docs-contributing:
14 :ref:`docs-code-of-conduct`. We expect everyone who interacts with the project
18 -----------------------------
25 One-time contributor setup
33 `new-password <https://pigweed.googlesource.com/new-password>`_ page.
34 #. Install the :ref:`gerrit-commit-hook` to automatically add a
35 ``Change-Id: ...`` line to your commit.
36 #. Install the Pigweed presubmit check hook with ``pw presubmit --install``.
37 Remember to :ref:`activate-pigweed-environment` first!
43 #. Run :ref:`module-pw_presubmit` to detect style or compilation issues before
46 #. Add ``gwsq-pigweed@pigweed.google.com.iam.gserviceaccount.com`` as a
49 #. Address any reviewer feedback by amending the commit
50 (``git commit --amend``).
56 -----------------------------
67 .. _gerrit-commit-hook:
69 Gerrit Commit Hook
70 ------------------
71 Gerrit requires all changes to have a ``Change-Id`` tag at the bottom of each
72 commit message. You should set this up to be done automatically using the
82 …f=`git rev-parse --git-dir`/hooks/commit-msg ; mkdir -p $(dirname $f) ; curl -Lo $f https://gerrit
86 Download `the Gerrit commit hook
87 <https://gerrit-review.googlesource.com/tools/hooks/commit-msg>`_ and then copy
92 copy %HOMEPATH%\Downloads\commit-msg %HOMEPATH%\pigweed\.git\hooks\commit-msg
94 Commit Message
95 --------------
96 See the :ref:`commit message section of the style guide<commit-style>` for how
97 commit messages should look.
100 -------------
104 #. Include ``No-Docs-Update-Reason: <reason>`` in a Gerrit comment on the CL.
107 * ``No-Docs-Update-Reason: formatting tweaks``
108 * ``No-Docs-Update-Reason: internal cleanups``
109 * ``No-Docs-Update-Reason: bugfix``
116 ------------
118 development workflow <http://ceres-solver.org/contributing.html>`_. Consult the
120 <https://gerrit-documentation.storage.googleapis.com/Documentation/2.12.3/intro-user.html>`_
124 ``gwsq-pigweed@pigweed.google.com.iam.gserviceaccount.com`` as a reviewer to
134 …<https://chrome.google.com/webstore/detail/gerrit-monitor/leakcdjcdifiihdgalplgkghidmfafoh?hl=en>`…
141 * The response time expectation only applies to Googlers working full-time
144 <https://gerrit-review.googlesource.com/Documentation/user-attention-set.html>`_
152 90% of changes on which a Googler working on Pigweed full-time is added to the
156 --------------------
158 <https://opensource.google/conduct/>`_ and the :ref:`docs-code-of-conduct`.
161 -------------------
176 // https://www.apache.org/licenses/LICENSE-2.0
194 # https://www.apache.org/licenses/LICENSE-2.0
203 -------------------------------------------
212 ------------------------
219 builds:`` message. All failures must be addressed before submitting.
228 ------------------------
232 pass. If a project cannot build against Pigweed's tip-of-tree, it will stay on
248 In these situations, Pigweed's commit queue submission process will fail for all
254 ------------------------
255 To speed up the review process, consider adding :ref:`module-pw_presubmit` as a
262 $ pw presubmit --install
281 $ git push origin HEAD:refs/for/main --no-verify
290 $ git checkout -b myfeature origin/main
299 ``-b commit, --base commit``
301 branch of the current branch. Set commit to "HEAD" to check files added or
302 modified but not yet commited. Cannot be used with --full.
304 ``--full``
306 --base.
308 ``-e regular_expression, --exclude regular_expression``
312 ``-k, --keep-going``
315 ``--output-directory OUTPUT_DIRECTORY``
318 ``--package-root PACKAGE_ROOT``
321 ``--clear, --clean``
324 ``-p, --program PROGRAM``
327 ``--step STEP``
330 ``--install``
331 Install the presubmit as a Git pre-push hook and exit.
333 .. _Sphinx: https://www.sphinx-doc.org/
335 .. inclusive-language: disable
337 .. _reStructuredText Primer: https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html
339 .. inclusive-language: enable