I have wrongly deleted organization (created in GitHub). How to restore the deleted organization? I have access to my GitHub profile.
As long as you do not have an GitHub Enterprise Server license, you cannot restore the organization, as written in the delete section of an organization:
Once deleted, it will be gone forever. Please be certain.
If you do have an GitHub Enterprise Server license, you can follow the official documentation Restoring a deleted organization.
Related
I have a private github repository and in that repository there are some collaborators. They can't create new packages but they can publish to existing packages created by me as I'm the creator of the repository.
Is there any way that my collaborators will be able to create new packages and publish.
I was facing the same "create_package" permission issue. I think external collaborators were able to publish new packages in the past. But this no longer works.
Here's the response from GitHub's support team: "In order to publish an org scoped package, the actor performing the publish should be a member of the organization."
So the short answer to your question seems to be "no", at least for scoped packages (which it was for my case)
I have created a demo organization in my personal github account and transferred the ownership of one of my pet-project repositories to that organization.
After that I have added one of my colleagues as a member in my newly created demo organization and tried publishing an npm-package.
Voilà it worked, we were able to successfully publish an npm-package after being a member of the organiztion.
I have migrated a repo from on-prem hosted GHES (Github Enterprise Server)to GHEC (Github Enterprise Cloud), and it is accessible in GHEC.
We are now trying to archive the old GHES repo, but we are unable to because of the message on the repo page that reads
"
This repository is currently being migrated. It's locked while the migration is in progress."
I am unable to go to the "Settings" for this repo due to restrictions of my workplace, as I'm not an admin on the repo I believe.
Wondering what needs to be done to Stop the migration (even though it's already done), so that we can archive this repo.
Thanks for your help!
Screenshot of the message:
As noted in your GitHub discussion:
A user with GitHub Enterprise Server Site Admin access can unlock this repository by going to the Site Administrator page for the repository.
The URL should look like:
https://[hostname]/stafftools/repositories/[owner]/[repo]/admin
Once there they will see the unlock option under the Single Repository Lock section on that page.
Which means... you need to contact your on-prem GHES site admin to resolve this locally.
In case a project and organization got deleted by mistake, How to recover deleted project and organization in Azure DevOps?
If your project or organization is deleted within 28 days, you can recover it in a few steps.
For organization, I advise you to check Microsoft documentation.
For projects, it is very simple, regarding Microsoft documentation.
Click on Organization settings
Click overview and there is a category called Recently deleted projects with a list of projects that you can recover.
Enjoy.
As the title describes, I did so but the problem remains with the log:
batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.
So is there a way that works? I don't need to retain the history of the repository or any contents within it, since it is only used to store & publish on-line built binaries. Purchasing more data packs and bandwidth is not an option for me either.
GitHub's Git LFS quota is per-user account. It resets once a month, and then you get another free gigabyte of download. It doesn't matter how many repositories you have, and deleting them doesn't help.
In general, Git repositories, whether using Git LFS or not, are not a good fit for storing binaries. If you're using a GitHub repository, you can use release assets for binaries built from your repository, which are available without charge. If you're just trying to upload and distribute binaries, a different approach would be warranted, such as a VPS with a web server or a cloud bucket.
On GitHub sadly, a private repo is for premium users, and i uploaded a repo, but it has lot of login third party, and i want to make those login information private, and i have a MongoHQ connection, and want to make the database private, to deploy it on CloudControl.
How CloudControl and Heroku work, is that by taking the file AFTER the clone on disk or the clone is only 'temporary' file, and they take the one hosted on Github?
There is no need to have any credentials in the repository. It's actually highly discouraged to do so. The recommended way is to have your code read the credentials from the environment.
Refer to the Add-on credential section in the documentation for more details: https://www.cloudcontrol.com/dev-center/Platform%20Documentation#add-on-credentials