...est is created by volunteers using a web application called [http://enzyme.commit-digest.org/ Enzyme] (written by Danny Allen).
...nded to subscribe to the [https://mail.kde.org/mailman/listinfo/digest KDE Commit-Digest mailing list] and read the guidelines provided in the ''Documentatio
...
2 KB (208 words) - 10:48, 1 June 2018
=== Never commit code that doesn't compile ===
...les with your local setup. You should also consider what consequences your commit will have for compiling with the source directory being different from the
...
14 KB (2,277 words) - 16:49, 28 November 2023
#REDIRECT [[Commit Digest/Guidelines]]
...
38 bytes (4 words) - 23:11, 30 January 2011
[[Commit Digest| << back]]
Composing better guidelines for reviewing and classifying commits for the Commit Digest. The source of the original inclusion guidelines can be found [https
...
7 KB (1,223 words) - 17:35, 9 November 2012
-
1 KB (217 words) - 16:12, 8 March 2016
[[Commit Digest| << back]]
...any mentions of the publication, always either '''KDE Commit-Digest''', '''Commit-Digest''', or '''Digest''' (note the capitalisation and hyphenation)
...
6 KB (995 words) - 18:51, 8 June 2011
[[Commit Digest| << back]]
Some notes for developers on how to increase chances that a commit message is included in the Digest:
...
1 KB (177 words) - 10:07, 25 April 2011
[[Commit Digest| << back]]
...ugs you find that Danny is unaware of here (also send an email to danny AT commit-digest _DOT_ org so I know about it!):
...
2 KB (338 words) - 05:18, 18 May 2016
[[Commit Digest| << back]]
* '''[http://commit-digest.org/issues/2011-04-17/ Issue 179]''': -
...
2 KB (248 words) - 10:11, 25 April 2011
-
704 bytes (110 words) - 03:42, 21 December 2012
[[Commit Digest| << back]]
...ant commits that have happened recently or are shortly expected. Since the commit digest is probably read by people who have a strong interest in the actual
...
729 bytes (129 words) - 23:46, 22 February 2011
This page is about giving hints on how to write a meaningful commit messages that can be easily use for a filling the change log.
The commit message can also contain more specific information that wouldn't belong to
...
939 bytes (164 words) - 23:03, 18 December 2010
-
399 bytes (49 words) - 19:18, 26 June 2011
...est is created by volunteers using a web application called [http://enzyme.commit-digest.org/ Enzyme] (written by Danny Allen).
...nded to subscribe to the [https://mail.kde.org/mailman/listinfo/digest KDE Commit-Digest mailing list] and read the guidelines provided in the ''Documentatio
...
2 KB (208 words) - 10:48, 1 June 2018
...added the explanation into the manual, please mark the commit as ''Accept Commit''
...he both requests, so please also do the social media publishing before the commit goes out of search :)
...
559 bytes (89 words) - 20:04, 1 August 2016
[[Commit Digest| << back]]
Some notes for developers on how to increase chances that a commit message is included in the Digest:
...
1 KB (177 words) - 10:07, 25 April 2011
[[Commit Digest| << back]]
...ant commits that have happened recently or are shortly expected. Since the commit digest is probably read by people who have a strong interest in the actual
...
729 bytes (129 words) - 23:46, 22 February 2011
.... So far it has been developed in a separate repository, with a noteworthy commit history which ideally should be kept exactly (e.g. if multiple authors comm
...d way is to import the unmodified history of the subtree and to do a merge commit to move the merged repository to the plugin subdirectory.
...
2 KB (324 words) - 13:15, 9 October 2018
...p=phonon-gstreamer.git&a=commit&h=0bf6eb925dbbb4719a2789e53fd3a60eb8adfc26 commit 0bf6eb92]]
...
741 bytes (97 words) - 12:12, 7 September 2014
...ur merging commit. If he did, reset your current head to the latest pushed commit
...hen you land the patch with arcanist, this text will be used for an actual commit. Use the following structure:
...
4 KB (673 words) - 10:24, 20 February 2018
=Git for frequent contributions (or patches with more than one commit)=
...git.reviewboard.kde.org ReviewBoard] for revision. A rekonq developer will commit it when necessary.
...
3 KB (519 words) - 18:34, 18 March 2016
[[Commit Digest| << back]]
...ugs you find that Danny is unaware of here (also send an email to danny AT commit-digest _DOT_ org so I know about it!):
...
2 KB (338 words) - 05:18, 18 May 2016
...p=phonon-gstreamer.git&a=commit&h=0bf6eb925dbbb4719a2789e53fd3a60eb8adfc26 commit 0bf6eb92]]
...
1 KB (142 words) - 12:12, 7 September 2014
**{{commit|kexi|2fbb864}} Make project navigator's "single click" mode work on Windows
**{{commit|kexi|d5aae07}} Use the only supported style (breeze) on Windows and Mac
...
7 KB (1,042 words) - 10:22, 29 January 2018
== KDE Commit Hooks ==
The commit hooks are a set of scripts which are executed on KDE's Git server when you
...
5 KB (779 words) - 04:32, 25 January 2011
** {{commit|kexi|6a3fe65}} Avoid displaying "(I18N_ARGUMENT_MISSING)" for one complicat
** {{commit|kexi|c9e6040}} Remove unused & outdated check for MarbleControlBox::setMarb
...
6 KB (870 words) - 10:26, 29 January 2018
The biggest question is when to use the review board and when to commit directly.
* You want to commit in some of the libraries (files under libs/), namely main, flake, kotext, o
...
2 KB (396 words) - 21:17, 13 December 2010
This page is about giving hints on how to write a meaningful commit messages that can be easily use for a filling the change log.
The commit message can also contain more specific information that wouldn't belong to
...
939 bytes (164 words) - 23:03, 18 December 2010
=== Git Commit Policy ===
Prefix according to component the commit is about:
...
977 bytes (139 words) - 14:40, 14 March 2015
Status: published but needs more active maintainer (the newest Sharan's commit comes from 2008)
...
284 bytes (45 words) - 18:16, 6 April 2023
https://cgit.kde.org/falkon.git/commit/?h=pshaw&id=630a57edbc4eeed53b4a1fbf86707783e534f290
https://cgit.kde.org/falkon.git/commit/?h=pshaw&id=81d0fa9f20d04a098992e20776e2f6be59b92621
...
3 KB (545 words) - 18:34, 21 July 2019
===Commit list===
...
3 KB (419 words) - 17:36, 11 April 2023
...of the developer. Certain hooks must be successful in order for a push or commit to be accepted.
...tter of every Git commit. This is necessary to allow for the author of the commit to be reached by contributors later in time. A name is considered valid if
...
5 KB (896 words) - 22:31, 22 October 2022
