The GNOME GitHub Mirror

The GNOME Infrastructure is currently managing a mirror of git.gnome.org on GitHub.

Go to the git.gnome.org mirror in GitHub

FAQ for Users

Will pull requests and issues be accepted?

No, they won't be accepted. Issues have been disabled already while pull requests can't be removed on a per-organization basis but still the GNOME maintainers and developers will keep using the current workflow for reviewing and eventually accepting patches coming from GitHub's users.

How can I contribute in the case I have a patch handy?

After forking the repository and preparing your patch, you can submit it for review on the GNOME Bugzilla instance available at https://bugzilla.gnome.org. Make sure to select the correct product (which corresponds to the repository name of the specific GNOME module you are contributing to) and add the [PATCH] prefix to the title of your new bug request.

My pull request(s) were automatically closed by the GNOME Sysadmin Robot, what now?

If any of your pull requests were closed with the text that will follow it means you were suggested to start contributing via the ordinary means to the GNOME Project. The way to properly contribute to the project expects you to register an account on Bugzilla and follow the instructions available on the wiki.

Behind the automatic closures of Pull Requests there's a script that runs daily at midnight. The script was originally announced on the desktop-devel mailing list in November 2016.

The text we're currently using when closing a pull requests is:

Thank you for contributing to $project_name!

$project_name uses Bugzilla for code review.

If you have never contributed to GNOME before make sure you have read the
getting started documentation:
http://www.gnome.org/get-involved

Otherwise please visit
https://wiki.gnome.org/Newcomers/CodeContributionWorkflow
and follow the instructions there to upload your change to Bugzilla.

FAQ for GNOME maintainers

Why my module is not appearing on the mirror?

Modules are created and updated on-the-go when a specific commit gets pushed to a repository. Make sure that your repository receives a new commit after the 15-08-2013, which is the date we effectively activated the GitHub's hook on the whole set of repositories.

An old or obsolete repository was mirrored, what should I do?

Open a bug against the Sysadmin product here asking for the specific repository to be removed from GitHub. In addition to that, please also request (on the same bug report) the repository to be archived on git.gnome.org.

I am interested in contributing to the mirroring tools, where can I find them?

The hook that we are currently using is available on the following repository.

Sysadmin/GitHub (last edited 2016-12-05 14:22:47 by AndreaVeri)