In my list of repos I have an old repo that I worked on for 1 hr.
I would like to not see it anymore, I would like to not be involved with it anymore, I want it off of my screen.
How do I do it?
Here is a screen of my repo list:
It sounds like you want to delete the repo. That will completely remove it though, not only from that list. You won't be able to access it again.
You might want to save of backup first if there is any chance you will want to access it later, especially if the work you did hasn't been pushed into the project that you forked it from.
You can delete a repo by going to the "Settings" page for that repo (click on the repo in that list and "Settings" is a tab on the next page), then scrolling all the way to the bottom and clicking on "Delete this repository".
I think what you are wanting to ask is how to delete a GitHub repository.
Deleting a repository as #Paulpro rightly said will remove all your data from the given account so if you need any data it will be wise to take a backup.
How to delete a Github Account:
Login to your Github Account
Open the repository you wish to delete
On the menu of Repository click on Settings (the menu contains commits, settings, contributors etc.The last tab is settings there.)
Scroll down to the very bottom, the last option will be delete repository, click on that
In a confirmation box that comes enter the repository name as it is and then confirm to delete the repository.
Note These steps are to delete a repository.If you just wish to hide a repository from the public you will need a private repository option which requires a paid Github Account.
Related
I created a repository on GitHub and want to add a couple of friends to review my pull requests.
I used this source and when I enter the names of some GitHub users the Reviewers bar stays empty.
How to add arbitrary reviewers to my GitHub repository?
You can simply send the pull request link to your friends, then they can click the files changed button at the top:
Then, they can look through the diffs, and click the blue plus button on any line where they want to leave a comment:
Then they can click it, and add a comment and start a review:
You don't need to formally invite them since anyone that can read the repository can review pull requests. If you want to give them a github notification, you can mention them in the comments.
I can't seemed to find this information anywhere, but just wanna ask that if you are a contributor of a project and you worked on it so you can see all of those contributions on the chart, but then for whatever reason the owner of the project removed you, do you lose all of those contributions? as in will those green contribution grids(the days you work on it) go back to grey?
No, the contributions are based on the commit email ID, and do not have anything to do with the corresponding GitHub account having access to the repository. GitHub attributes a commit to a particular account if the email ID used with the commit is registered under that account.
So, unless the email IDs of past commits are in some way changed later, the contributions will still be visible, as long as the repository is public.
This also works the other way around. Anyone can set any email ID in their git configuration while committing, so it is trivial to falsely attribute commits to someone else, when viewing the contribution chart in GitHub.
We are setting up a open source project which we would like to allow freelancers to develop alongside us without damaging anything.
In general can the collaborators make changes to repositories without admins being able to check the changes over before code is merged into master.
What is the best method to use to prevent the repository from user damage whilst working with a large number of public freelance developers / users?
What you can do is you can give them read-only permission. They can fork to their own account and start working on that code. Then after finishing a feature they can create a pull request to merge it back to the main repo.
For a Personal account on Github, there are two types of 'roles' - Owner and Collaborator.
For a full list of who can do what - see here:
https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository
To answer your question - "No - A collaborator cannot delete a repository"
I am a collaborator on a private repo, but it doesn't show up under my repositories. I also cannot see it on the other user's repository listing because it is private. I have confirmed that I am able to push/pull to the repo. Is there a way to access this repository using Github without typing in the full URL ?
You can see the repositories where you're a collaborator. To do this, head to the Repositories section of your account's settings (https://github.com/settings/repositories).
There should be a Leave action button aside each repository you're a collaborator on.
Even though it won't show up in YOUR repositories, it should appear on your github dashboard (click the github logo), on the bottom right. There should be a list that has buttons at the top to filter all, public, and private repos. Try clicking the private button and it should be there.
Note that if you have opted in to the new dashboard, the above doesn't apply, but you can see the repositories (owner and collaborator) on the left..
A simpler place (as per today) to find private repositories you are collaborating on is to go to https://github.com/ (do not include your username, but make sure you are already logged in). On the left hand side, you can find a search interface or click "show more" to see them all.
It's weird that as per today, if you try to do this from the Repositories you won't find them.
Is posible to integrate the project issue tracker of Github into Netbeans to automatize the add, change or remove issues trough the IDE.
Thanks
It seems the current answer is no (at least I could not find anything in the mailing list or even the bug database)
Therefore I opened a corresponding report for an enhancement. Feel free to register and vote on it.
It's not really needed to have this integration, since you can comment on or close GitHub issues through the git comment.
Examples:
Reimplement feature XYZ as described in #123
Removed extra spaces in foo. Fixes #148
Working on integration with bar. #99 and octocat/bar#20
Read this blog post
This integration is available in NetBeans 12.
From the Window menu, select Tasks. In the Tasks tab, add a repository by clicking the icon on the right side of the repository header.
A dialog appears. Select GitHub Issues as the Connector.
You'll need an OAUTH token, known as a GitHub Personal Access Token. To create one, visit github.com, log into your account. Click on your account icon in the upper right corner and select Settings from this pulldown menu.
Now click Developer settings on the navigation menu on the left. Click Personal access tokens on the new menu on the left. Click Generate new token. Put a descriptive name in the Note field.
Select the appropriate permissions. Unfortunately I'm not certain what minimum permissions are required, but those I selected, which seem to work, are: notifications, read:discussion, read:enterprise, read:gpg_key, read:public_key, read:user, repo, workflow. Thanks in advance if you can provide further insight here.
Next click the Generate token button. You'll be presented with the token secret once and only once. Copy it and paste into the Oauth Token field in the NetBeans dialog from above. Click Add repository.
A dialog appears prompting you to select the username and repo for which you'd like to track Issues. Choose one and click Ok. This will populate the remaining fields in the Create Task Repository dialog. Click Connect to verify and you should see a success message.
Click Ok on the popup, and again on the dialog, and you should see your new repo and list of Issues.
And that's it. You can now open Issues, assign them, add comments, manage labels, change issues to PRs, create milestones, manage templates, and so forth.