The github Desktop program has an automatic naming scheme for local repositories, and I can't find a way to change them manually.
Consider this screenshot of the sidebar,
with 4 identical names, it's quite hard to navigate. Those folders are different copies (different branches, actually) of a common repository 'papers', under the 'plasmonics' organisation. Strangely, not all repositories of that organisation appear with the plasmonics/ heading in the sidebar, and I can't tell what triggers a difference. In any case, I'm hoping to find a way to rename those sidebar names manually. Is it possible?
You cannot rename those sidebar names, but do check if the issue persists with the new GitHub Desktop application (released in Sept. 2017, two years after your question)
It should be able to display/filter those repos correctly.
For local repos, make sure those copies are done through the git worktree command (Git 2.5 and more, from July 2015). That allows to clone a repo once, but check it out multiple times (one folder per branch).
There is a pending issue (907) for de-duplicating the display of those worktrees.
Related
We have some repos that we no longer need to keep on GitHub. If we use GitHub's archiving feature, the repos actually stay online. What we'd like instead is a way to download an archive of all the content (including issue reports) for a given repository, put that repository archive in a long-term preservation system, and delete the repo from GitHub. This is more than simply backing up a repository in the sense of other similar questions on Stack Overflow, and is more like what BackHub can do. Is there a tool or set of procedures (beyond git clone) that will allow me to do this?
python-github-backup can back up a single repository in an organizational account, as well as all repositories in an account. I have tried it on individual repositories, and it worked as hoped: using its --all option, it captures issues, labels, milestones, pull requests, and wiki pages, as well as the repo itself.
Googling "github-backup" leads to other similar tools, but most of the others seem to have fewer features than python-github-backup or haven't been updated for many years. However, I must admit I haven't explored the other options very carefully.
Tip: the essential ingredient in using Google to find a suitable tool seems to be to search for the words "github" and "backup" specifically, and not include "archive" as I was doing in my original search, or even use more elaborate search strings such as "how make backup github repository".
If is preferable to use git clone --mirror, to get the full repo history and then
git bundle --all to get only one file (easier to store than a collection of files)
a long term storage system (example AWS S3)
Notes:
you might want to clone the associated GitHub wiki as well, if you have one.
that won't preserve your issues/Pull Requests
Use a folder on your local machine, google drive, or dropbox. No need to use github on non-active projects.
I'm using Eclipse importing TFS projects, one project is:
$/product mapped to C:\dev\product
I opened a branch and started working on different workspace:
$/product-branch mapped to C:\dev-branch\product
I worked on each project successfully
But now in branch in TFVC Pending Changes I see changes I made (checkouts) also in C:\dev\product ($/product)
Why am I seeing such changes and How can I separate those branches when I switch to different workspace?
EDIT
My TFS 2010 is using server workspace.
A TFVC workspace is the container for all of the work that should be grouped together (think of it like the contents of a Git repository). Now if you open a sub-folder of a Git repository in Eclipse and you've made changes at a folder that's higher up (that is, one you didn't explicitly open), the Git SCM still shows those files. It doesn't only show the files modified for the folder that you've got open. That's the same behavior as what the TFVC support is currently showing.
If you are using server workspace and checked out work under a different workspace, it will also show pending changes in pending changes list. Take a look at this similar issue: https://stackoverflow.com/a/423439/5391065
As a workaround, you could temporarily exclude no need changes in another branch to exclude list.
ALL,
I am managing multiple projects. All of them located on the GitHub and I'm using GitHub for Windows GUI and GitHub Shell.
Recently one of the projects got updated with the really big file name and so in order to keep the GitHub happy I had to move it from the standard place: c:\documents and settings\\My Documents\GitHub to just c:.
This created a disaster as I currently have two places to manage.
Is it possible to keep GitHub GUI happy and stop making new repository on the C:\? In other words, can I configure GitHub to use 2 source directories?
Thank you.
You can drag the root folder of a git repo (the one under c:\ in your case) from Windows Explorer onto the start screen in GitHub for Windows. Then it can see your repo and can manage it in your non-default location.
Not for a single repository.
You could move the entire repo to the C: drive.
Or you could manage 2 repositories, one in My Documents and the other on the C: drive.
Situation: I've cloned some repos from github, and I'm expecting them to be put in github tab, but they are only available in local repos tab. Their names still contain creators names ( someUser/someRepo )
Tried to clone with bash/clone to desktop button/drag&drop, and get expected same result.
link: http://img822.imageshack.us/img822/2912/uz4b.jpg
What I want: Cloned repos must be shown in github tab, separated by authors, with nice avatars and so on. (as it is shown on of website)
What I get: Cloned repos put in local repositories tab and messed up with oser dozens of local repos witch I create every 5 minutes for every task i need.
os winxp, app version 1.0.56.0
Thank you
According to github support, "Currently the 'github' tab only shows repositories that are under your account or under an organization that you belong to."
Maybe requested feature will be added later
I'd like to manage the GitHub wiki for my project at the same time as I'm developing the code. For example:
Branches
master (stable versions)
develop (development of next version)
Others... (Possible other dev / feature branches)
Ideally, I'd like the wiki to be contained in a subfolder (e.g. /wiki) of the project. Then when I'm making changes to the code I can also update the wiki as the same time (code + documentation change). It'd also mean that all my development code and documentation would be self-contained in the "develop" branch until I merge with the "master" branch. Hopefully, even if via a manual process, the GitHub wiki would then be updated after the merge with master to reflect the changes.
I've taken a look at Git's submodule feature, but from what I understand that usually points at a single revision. I'd like to somehow follow my code development so branching and merging would work as normal.
As explained in "True nature of submodules", you can make modifications and updates within a submodule, as long as you commit also the parent repo in order to record the new state of your "wiki" sub-repo.
If you intend to use Gollum to display and work on your GitHub wiki while it's on your local machine (you probably should), then you will have a trouble if you use submodules.
Gollum wants to do local commits to your local Git repository (but not pushes), but in a submodule .git is actually a file containing the local repository, not a true Git repository. This causes Gollum to break.
Submodules also have the problems that the versions aren't coupled to the parent repository, and they aren't completely de-coupled. It a nuisance to have the source code repository to want to push the new wiki version number (but not the wiki contents) every time you make a documentation change.
The solution I use is simply to clone the wiki repository into a directory inside the main project directory and add it to .gitignore. By using a consistent name for the directory across projects (e.g. github-wiki), the chance is minimized that the wiki won't be in .gitignore and gets accidentally uploaded into the main repository.
For consistency, his approach also works well for GitHub pages, although it's unnecessary as they don't experience the problem with Gollum.