I have a github account by my employer. I am working on a project single handedly. Now Is it possible that another employee uses the same account but different repository and does not have access to my repository?
On googling I found that this is possible if I convert my account into an organization account! So, yes this is possible.
https://help.github.com/articles/converting-a-user-into-an-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 just signed up for GitLab, after learning about this cool feature where you can import your GitHub repositories and keep the two in sync. The import feature seems simple enough, but I paused when I got to the step where I authorize GitLab to my GitHub account. Why does it need so many permissions? Some make sense to me, others not so much. Specifically:
Personal user data
Full access
This application will be able to read and write all user data. This
includes the following:
Private email addresses
Private profile information
Followers
I understand why it needs to read and write to all public and private repository data. It's moving all that data to GitLab, and it needs to write to keep it in sync. What I don't understand is why it needs write permissions to my email and profile information?
I know that GitLab is a reputable company that didn't just pop up yesterday, but I am still wary when giving full access permissions to any service. If someone could help me understand, that would be appreciated.
You have two options when migrating a repository from GitHub to GitLab. You can migrate using only the url, in which case what you’ll have on GitLab is more similar to what you’d get if you simply added an additional remote in the repo - the full repo will be there, but everything specific to GitHub - the pull requests, comments, issues, etc, as well as all users tagged or participating - will be lost.
Alternatively, you can use the GitHub importer. This option fully migrates the GitHub repo to GitLab, setting up the GitLab equivalents of GitHub features (pull requests become merge requests, etc.). And part of this involves assigning users to each comment, mention, PR, etc.
From the gitlab docs:
When issues and pull requests are being imported, the importer attempts to find their GitHub authors and assignees in the database of the GitLab instance. Pull requests are called merge requests in GitLab.
For this association to succeed, each GitHub author and assignee in the repository must meet one of the following conditions prior to the import:
Have previously logged in to a GitLab account using the GitHub icon.
Have a GitHub account with a public-facing email address that matches their GitLab account’s email address.
GitLab content imports that use GitHub accounts require that the GitHub public-facing email address is populated. This means all comments and contributions are properly mapped to the same user in GitLab. GitHub Enterprise does not require this field to be populated so you may have to add it on existing accounts.
So yes, these are required if you want the full GitHub mirror or migration. If you just want the git repo contents, use the import from url tool, and the requirements will be much less extensive.
I am new to GitHub and ran into a strange problem. I have a GitHub Enterprise account, and am trying to add other GitHub account users as collaborators to a repo. When I searched for their user names, it errored with a message "XXX isn't a GitHub member". I am very sure that the users I am trying to add just created free public accounts on Github.com and I am searching with the right user names. Can anyone shine some light?
Thanks,
Annie
GitHub.com and your GitHub enterprise are two completely different different instances. They do not share any user data.
This means to add a collaborator to a project on your GitHub enterprise instance the user needs to create an account on this GitHub enterprise instance and not on GitHub.com
Some time ago I started to use the Bluemix platform to develop PHP services that were used by a mobile application. After a while, I realized that it would be very useful to have a repository to which I can connect multiple Eclipse IDEs and work on the same application.
I already had a Jazz ID which was used for the work projects; I am talking about using Bluemix+Jazz for personal projects.
When I first connected the Bluemix ID with the Jazz ID, everything was well. But I realized that it might be a conflict of interest because I am using the same Jazz ID for both work and personal projects.
My question is: Is there a way to use a new Jazz ID in Bluemix?
It seems that the connection between the two IDs cannot be changed from Bluemix, DevOps or Jazz.net.
Costin, thanks for your interest in IBM Bluemix and the IBM Bluemix DevOps Services. Like Lauren has said, you'll probably want two IBM IDs, one for your work email address and one for your personal. They ultimately can be associated with two Bluemix orgs, each associated with a different DevOps user.
You'll need to decide which Bluemix org you want each of your apps to live in; the corresponding user should own the app's Git repository. To move a Git repository, you can use either of these approaches:
Use the repository's "Download the contents of this branch as a zip file" button to download the contents. Then as the other user, create a repository and import the zip file.
Share the repository with the other user, fork as the new user to get a copy.
Once you have the code in the other user's repository, redeploy to that user's Bluemix org.
Once you have everything where you want it, delete the stuff (apps and repositories) that are not where you want them.
One option is to create a new IBM id that is linked to your personal e-mail address. The IBM id could be used to sign in to Bluemix and DevOps Services.
I am setting up a private repository in GitHub and I want to invite people to my repo.
I found out that I can invite github users as my team members, but I want to know is it possible to invite non-github users to access my repo for checkin/checkout?
Thanks in advance.
You could add their ssh keys as Deployment Keys.
Deployment keys are ssh keys of users (usually, scripts) that are allowed to read the repository so they can build the code and deploy it somewhere.
This would allow your non-githubber coworkers to clone the repository.
Unfortunately, I don't think there's an equivalent system to allowing non-githubber to use the web interface.