Revision as of 22:40, 16 February 2021

GitHub Mirror

KDE is managing a read-only mirror of our repos on Github. It's located at https://github.com/KDE .

We want to make KDE sources easy to find, share and build upon; and most importantly we want your contributions to count towards your github profile. :)

FAQ

Why don't you enable pull requests?

Our central repositories are handled by our awesome sysadmins over on kde.org where we have full control and tighter integration within our services. If we start using multiple repositories and making developers look in two places that gets very complicated and unfair on the maintainers.

Also as an open source project, it's very important for us to keep to using open source tools. Github does not meet that requirement.

How do I submit “Pull Requests”?

The process of using GitLab is very similar to using GitHub.

Log in to KDE's GitLab
Fork the repository of the project you want to work on
Make a branch in your fork
Make changes, commit them to your branch, and push
When you push you should be given a link to easily make a merge request. If not, navigate to your fork on GitLab and make a pull request from there

How do I submit “Issues”?

Please file a bug report or wish at https://bugs.kde.org/

Where can I find the “original sources”?

All KDE Git repositories are available for browsing at https://invent.kde.org/.

For details on KDE's Git infrastructure see the dedicated GIT infrastructure page.

@@ Line 16: / Line 16: @@
 ==How do I submit “Pull Requests”?==
-KDE is in the process of moving many projects from [https://phabricator.kde.org/ Phabricator], our old code-management tool, to [https://invent.kde.org/ GitLab]. Currently some projects are still hosted on Phabricator while others are hosted on Gitlab.
-To determine which tool should be used for a particular project:
-# Look at the project's documentation (README.md, wiki page, etc.). It should tell you how the project wants to accept patches.
-#* Unfortunately, some projects documentation still needs updating.
-# Look at the listings of projects on [https://invent.kde.org/ KDE GitLab]. If the project is there, that is most likely where patches should be uploaded.
-#* Check and see if there are already merge requests on GitLab. If there are some, it is a pretty certain sign that the project is using GitLab.
-# Ask the project developers. We are always happy to talk with potential contributors and point you in the right direction!
-Follow the instructions below depending on which patch-uploading tool the project uses:
-=== For Projects using GitLab ===
 The process of using GitLab is very similar to using GitHub.
 * Log in to [https://invent.kde.org/ KDE's GitLab]
@@ Line 34: / Line 22: @@
 * Make changes, commit them to your branch, and push
 * When you push you should be given a link to easily make a merge request. If not, navigate to your fork on GitLab and make a pull request from there
-=== For Projects using Phabricator ===
-* Fork and commit your changes in your fork as before
-* Create an account on https://identity.kde.org
-* Run <code>git format-patch HEAD^</code> to create a diff
-* Learn [https://community.kde.org/Infrastructure/Phabricator#Posting_a_Patch_using_the_website how to format and post a patch]
-* Head to https://phabricator.kde.org/differential/diff/create/ to upload the diff.
-The maintainer for this software will then comment and merge your request.
-Alternatively you can use the command <code>arc diff</code> to streamline the process. More details are available in the [https://community.kde.org/Infrastructure/Phabricator#Using_Arcanist_to_post_patches Phabricator] page.
 ==How do I submit “Issues”?==