Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • development
  • v0.5.0
  • v0.4.9
  • v0.4.8
  • v0.4.7
  • v0.4.6
  • v0.4.5
  • v0.4.4
  • v0.4.3
  • v0.4.2
  • v0.4.1
  • v0.4.0
  • v0.3.1
  • v0.3.0
  • v0.2.10
  • v0.2.9
  • v0.2.8
  • v0.2.7
  • v0.2.6
  • v0.2.5
  • v0.2.4
22 results
Compare
user avatar
Prereq grammar fix
Sam Gleske authored
91f89d33
History
user avatar 91f89d33
History
Name Last commit Last update
docs
lib
scripts
.gitignore
CHANGELOG.md
LICENSE
README.md
RELEASE
add_mirror.sh
config.sh.SAMPLE
delete_mirror.sh
git-mirrors.sh
ls-mirrors.sh
update_mirror.sh
README.md

gitlab-mirrors

The gitlab-mirrors project is designed to fill in a feature which is currently missing from GitLab: the ability to mirror remote repositories. gitlab-mirrors creates read only copies of remote repositories in gitlab. It provides a CLI management interface for managing the mirrored repositories (e.g. add, delete, update) so that an admin may regularly update all mirrors using crontab. It operates by interacting with the [GitLab API][1] using [python-gitlab][2].

Features

  • Mirror different types of repositories: Bazaar, git, subversion.
  • When adding a mirror if the project doesn't exist in GitLab it will be auto-created.
    • Set project creation defaults (e.g. issues enabled, wiki enabled, etc.)
  • Update a single mirror.
  • Update all known mirrors.
  • List all known mirrors.

Three easy steps

  1. Setup prerequisites
  2. Install gitlab-mirrors
  3. Manage your mirrors

Note: if you are upgrading then see docs/upgrade for notes on upgrading.

Get help

There are a couple ways you can try to get help. You can file an issue. You can also join the #gitlab IRC channel at freenode.net and direct your questions to user sag47.

IRC Etiquette

  • I generally stay logged in to freenode so be sure to mention my handle when you're asking questions so that I see it in the #gitlab channel.
  • If I don't answer right away then just hang out in the channel. I will eventually write back to you as it just means I'm away from my keyboard, working on something else, or in a different timezone than you.
  • You should treat IRC as what it is: asynchronous chat. Sure the messages can be instant but in most channels people are in different time zones. At times chat replies can be in excess of 24hrs.

Contributing

I enjoy contributions and encourage them! You should add your code to my project and make your mark. Pick off an issue or implement a feature filling your need. I only make a few simple requests in order to contribute.

  • Test your own work before submitting a pull request. Most of this project is bash code so we do not have the luxury of a test driven framework to assist our development. Needless to say I will be sure to test it myself before it ever makes it into a production release.
  • Create a feature branch with a name that does not exist in any of my branches (e.g. feature/myfeature or feature-cool_feature). This is where you should do your development. This will allow you to integrate my development with your own and ease integrating updated code if we're both concurrently developing.
  • When your feature is ready make a pull request to the development branch. Pull requests to the master branch will not be accepted. The master branch is intended to drive production systems and only stable production-ready commits will be made to it.

Happy hacking!

License

Created by Sam Gleske under MIT License.

Contributors