As mentioned in this issue, that happens when you mirror a GitHub repo which has pull requests made to it. The refs beginning ‘refs/pull‘ are synthetic read-only refs created by GitHub – you can’t update (and therefore ‘clean’) them, because they reflect branches that may well actually come from other repositories – ones that submitted … Read more
Considering that the unit of work for git is a repository (or more precisely a repository content), I don’t think you can easily integrate one file. If you don’t need its history, you could consider simply copy it in your repo. But if you do need the history, then some git filter-branch (as in “git: … Read more
The *-dev packages most often contain the headers related to a library’s interface. Next most common are package-config files (*.pc) describing build options and staticly linked libraries. In general, if you want to know the contents of a package you have installed, dpkg -L pkgname will get you that. The apt-file program can tell you … Read more
Release repositories hold releases and Snapshot repositories hold snapshots. In maven a snapshot is defined as an artifact with a version ending in -SNAPSHOT. When deployed, the snapshot is turned into a timestamp. By definition, snapshots are mutable, releases are immutable. This is why Nexus makes you store them separately because usually you don’t care … Read more
Also, you can use -o or –offline in the mvn command line which will put maven in “offline mode” so it won’t check for updates. You’ll get some warning about not being able to get dependencies not already in your local repo, but no big deal.
Your example terms; DataMapper, DAO, DataTableGateway and Repository, all have a similar purpose (when I use one, I expect to get back a Customer object), but different intent/meaning and resulting implementation. A Repository “acts like a collection, except with more elaborate querying capability” [Evans, Domain Driven Design] and may be considered as an “objects in … Read more
You can have as many remotes as you want, but you can only have one remote named “origin”. The remote called “origin” is not special in any way, except that it is the default remote created by Git when you clone an existing repository. You can configure a second remote, push to/pull from that remote, … Read more
You can transfer those (simply by adding a remote to a GitHub repo and pushing them) create an empty repo on GitHub git remote add github https://[email protected]/yourLogin/yourRepoName.git git push –mirror github The history will be the same. But you will lose the access control (teams defined in GitLab with specific access rights on your repo) … Read more
A GitHub repo in itself isn’t connected to anything, it only contains a set of files. If, amongst those files, you have several Aptana projects, you can use those once you have clone locally. However, if you want to clone only a part of the GitHub repo in order to get only one of those … Read more
The reason most people advise to do separate repositories is because it separates out changes and change sets. If someone makes a change to the client projects (which you say doesn’t really effect others), there is no reason for someone to update the entire code base. They can simply just get the changes from the … Read more