My repository in the github had been deleted.
The code was recovered, but we had a lot of Github issues i'd like to recover, is there a way to recover them once deleted?
Thanks.
You need to email support#github.com as soon as possible when this happens.
I accidentally deleted our main GitHub repository instead of my own fork. I emailed support#github.com like Paul Betts suggested.
After about 10 minutes the support replied and the original repository was recovered.
I accidentally deleted my important repository and when tried the above-suggested methods, got to know that the process has been updated.
Please follow the steps provided in the link to recover the repository all by yourself.
Link - https://docs.github.com/en/github/administering-a-repository/restoring-a-deleted-repository
Note - You can only restore repositories that have no forks or have not been forked. (As per mentioned under Settings >> Repositories >> Deleted Repositories section)
Also, for any Github-related support requests, one needs to raise the support request through Github's support website.
Link - https://support.github.com/ (works for any GitHub related support)
Related
I'm trying to fork this repository, but getting an error message:
You can't fork this repository at this time.
I've read the license, and tried forking from another computer using VPN, in case of security conflict of my browser and GitHub, but it still don't work, and I can't even guess why so. Please tell me, what am I doing wrong?
This also happens if the user has blocked you
Tested today, May 2021.
A similar related message if you try to open an issue on a repository whose owner blocked you is:
You can't perform that action at this time.
You can just manually create a new repository and reupload the code there however. You just won't be able to send pull requests.
That sounds like a temporary GitHub issue.
Creating a fork isn't dependent of a license or vpn. It's just a http call in your browser.
Update: I forked the repo without issue.
If you already have a fork of the original repo, you cannot have another fork.
You can add the other repo as a remote though and use code from there.
I have created a personal website in R studio and committed it to Github.
It is not loading at all, and can not figure out why it is not working.
The link to my github repository is https://github.com/CPRyan/CPRyan.github.io
I'm sorry I can't provide more details, but I really do not have any clue where to start.
Update:
It's not because I haven't configured the options:
Update 2:
https://cpryan.github.io does not work but, https://cpryan.github.io/index does!
Not sure if that helps.
In my case it was helpful:
git commit --allow-empty -m "Trigger rebuild"
git push
Simply committing to Github is not enough. You need to configure Github Pages to publish your site.
See this link.
Also, Index.html should be index.html (not capitalized)
I managed to solve this through trial and error.
I'm learning, so my process for creating my repository on github and on my local directory was messy. I still lack the knowledge to explain what the issue was, but here is what solved it.
I pulled from the github repository, merged, and then pushed the whole thing back online with commit and push. I guess this merged the two, "solved the deltas", and integrated it into a functioning set of files. Apologies for the terrible explanation but now it works!
Thanks to #Kevin Kang for pointing me in the right direction.
Because we've done some rearranging of our documentation setup, I have two separate read the docs projects which I need to build from the same GitHub repo. One of them is brand new, and the other used to be pointed to the old repo.
I have set up a webhook on each project, and added both these webhooks to the repo.
The problem is that in the project that used to be pointed to the old repo, the stable build is still associated with the SHA of the latest release on the old repo, which does not exist in the new repo. This causes the stable build to fail.
One other thing I hope to solve, when activating some of the new versions (which used to exist in the old repo) an "_a" is added to then of the published version name, even though there are not multiple publishable versions with the same name.
I'm wondering: is it possible to completely refresh all of the RTD-detected versions and tags? I think doing so would solve both these issues.
I've tried "wiping" the builds but that doesn't help, I have read the RTD docs on versions many times, and I've triggered new push events from github (which are sent and received successfully) but still can't make any progress.
The best way to solve this turned out to be just recreating the RTD projects. If anyone else comes across this issue, you could check out the ticket I made on the RTD repo https://github.com/rtfd/readthedocs.org/issues/3763.
Trigger a Build on any of the existing versions that RTD knows about. After that build job starts the Versions list will be updated from the git repo.
I wanna migrate a project from Assembla to Github with all its tickets and sources.
Sources
The sources are not the problem because I can push it easily to the new environment.
Tickets
My problem is the linking between commits that includes an issue number (e.g. #123 Increased build number) to the related issue / ticket.
Github counts everything in its ID (tickets, pull requests, etc). That means that it seems to be highly unlikely that my Assembla ticket #123 will be my Github issue #123 and therefore the connection between he commit and the ticket will break.
I tried to export all my tickets from Assembla but label Backup successfully scheduled. stays for hours now.
Question
Please correct me if this assumption is false. My question at all is, if someone could provide an idea how to solve the problem. It seems to be that there is no official importer to Github or exporter from Assembla.
You are right, official importer from assembla to github does not exists. So you need to do it manually(implement utility) consuming assembla api to pull information and upload it to github. You can try to find existing hand made tools here
Please correct me if this assumption is false. My question at all is,
if someone could provide an idea how to solve the problem. It seems to
be that there is no official importer to Github or exporter from
Assembla.
I couldn't find an answer or a solution that included migrating both source code and issues (tickets). Here is an article I wrote with a complete solution.
Github counts everything in its ID (tickets, pull requests, etc). That
means that it seems to be highly unlikely that my Assembla ticket #123
will be my Github issue #123 and therefore the connection between he
commit and the ticket will break.
I found a solution for that as well. There was a need to create an automatic script (in Python) for associating Assembla Tickets' attached files with these files after being added to the Github's Issues, and that includes:
- Handling updates in Tickets
- Handling labels
- Handling references between Tickets
- Handling references to Commits.
- Preserving the original Tickets numbering after migrating them as Issues to Github.
The process includes:
Creating a backup of all Tickets (which unfortunately doesn't contain any images or attached files). Following your question, you need to go to Settings and schedule a backup for your tickets, and then visit again this page and download it. The backup should be a .bak file.
Importing the Assembla repository from Github's new repository.
Customizing the scripts, as explained in this article.
Running our script which handles all the rest via automation.
Optionally:
Updating existing Issues in a Github Repo
As you know GitHub has introduced a Repo Transfer feature. https://github.com/blog/876-repo-transfers
This allows you to change ownership of your root repos, not forking them with your organization. However, if you have already forked a repo and want to dump all its open issues to newly created one, what should you do?
Is there any solution on GitHub-2-GitHub issues import?
Though Tekkub answer makes sense, I still implemented a short script to transfer issues:
github.com/..../gh-issues-import
You should delete the newly created one and transfer the repo instead. Transferring repo ownership takes the issues with it.
Tekkub wrote a not-so-well-received answer (-2 as of this writing): "You should delete the newly created one and transfer the repo instead. Transferring repo ownership takes the issues with it." He isn't wrong; he just didn't walk through any of the considerations and gotchas. I'll enumerate a few of those below ...
Only Works if you have "admin" access to the parent repo:
In my case, I couldn't use repo-migration because I don't "own" the parent repo so I can't authorize the transfer (parent repo in the hands of a team-member who left). So it doesn't work for me. HOWEVER ... if you do in fact have admin privileges to the parent repo you are migrating, then using the "transfer repo" function is distinctly better and nowhere near as hard as it sounds.
Git history - trivial to keep
One of the commenters expressed concern over the new repo having its own history they don't want to lose. Well, that's the magic of git as a distributed VCS. You simply pull down all branches and tags and everything else to your local repo and then push that history up to the repo you are going to migrate.
git remote add origin1 https://github.com/blah/blah
git remote add origin2 https://github.com/blah/blah
git pull origin1
git push origin2
If you've created issues in both repos ... well that's screwed
Decide which repo has more important content, use that as the base, and port everything else into there. It's a "merge". good luck. The gh-issues-import.py script script posted by ibo.ezhe helps, but it doesn't restore comments on the issues. Feel free to improve it and send him a PullRequest (I did).
There's a Chrome Extension called Kamino that my colleague wrote. It's open source, and works extraordinarily well. It's more for copying issues individually, but he's looking at doing bulk copies as well.
Available here: https://chrome.google.com/webstore/detail/kamino/ffdebockfdjileaojbbccofhgncmioaf
Source code:
http://github.com/gatewayapps/kamino