I followed the guide here https://docs.github.com/en/free-pro-team#latest/actions/learn-github-actions/sharing-workflows-with-your-organization.
I successfully created a GitHub Organization shared workflow and can access this shared workflow if I create a public repo under the organization or my account (I am a member of the organization).
However, if I create a private repo I do not see the shared workflow. I am using the free-tier for my membership account and organization, so I'm not sure if that is the issue. There was no documentation stating that was a requirement.
Only possible in GitHub Enterprise plan organizations:
to use templates to create workflows in private repositories, the organization must be part of an enterprise plan.
GitHub documentation
You can also create workflow templates in the .github repository and
share them with other users in your organization.
https://docs.github.com/en/actions/learn-github-actions/sharing-workflows-with-your-organization
You can also create workflow templates in the .github repository and
share them with other users in your organization.
Related
Similar to Github Cloud is there a way in Azure Devops to create internal repos wherein multiple users can have access to some repos which have certain documents without adding them as users or groups to such repos? If we make RepoA as internal it should be available to all users under an org without specifically adding them.
In Azure DevOps, for public projects, any user can get access your public project and check Git repo without signing in or added as a user in your org. You can also refer to this doc: Make your private project public - Azure DevOps Services Public Project | Microsoft Learn .
If for private projects in Azure DevOps, firstly, users must be granted access to the specified private project also as Basic access level in your org via navigating to Organization Settings -> Users -> Select the specified user -> Manage user to set users' access level.
Users be with Stakeholder access level, they will not be able to use Azure Repos for your private project.
Otherwise, to set permissions for a specific repository or some specific users, navigating to Project Settings -> Repositories -> Security to manage the permissions.
You can also refer to: About access levels - Azure DevOps | Microsoft Learn and Set Git repository permissions - Azure Repos | Microsoft Learn
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.
We created a public .github repository in our organization in order to create custom starter workflows as per:
https://docs.github.com/en/enterprise-cloud#latest/actions/using-workflows/creating-starter-workflows-for-your-organization
but can't seem to see them when creating a new repo.
Here is our github repo https://github.com/pepsico-ecommerce/.github
but can't seem to see them when creating a new repo.
Check if the new repository created is a public or private one, and test it for a user (outside an organization).
The documentation does mention:
Starter workflows created by users can only be used to create workflows in public repositories.
Organizations using GitHub Enterprise Cloud can also use starter workflows to create workflows in private repositories.
Your use-case seems to match the first scenario, since you are not using GitHub Enterprise Cloud.
Meaning a .github/workflow-templates would not work on github.com.
It would on a GitHub Enterprise Cloud instance.
is a "Public" DevOps project accessible by
everyone on Azure DevOps
only by the organization members
all members of the Azure Active Directory that is linked to the organization.
What I want to achieve is 3. over 2. but not 1.
Thank you
A public project means "Anyone on the internet can view the project. Certain features like TFVC are not supported." which is the 1 in your list, this you can see when you create a new project in Azure DevOps service :
You can find more detailed informaion at the doc What is a public project?, it says "Users that aren't signed into the service have read-only access to public projects on Azure DevOps.".
What I want to achieve is 3. over 2. but not 1.
only by the organization members
all members of the Azure Active Directory that is linked to the organization.
What you are seeking for is a private project in fact, create a new private project and add the organization users to this project, or if your organization is connected to AAD then you can directly add anyone who's in the AAD to this project with no need to add them to your organization first.
This you can find more information at the doc Add members to your project.
It seems for public project to access, admin/project owner need to invite the required user.
Ref: https://learn.microsoft.com/en-us/azure/devops/organizations/public/invite-users-public?view=azure-devops
Public projects are not that public...
I have a setup on Devops where I want to give and external account (not part of the company) access to the repos. I thought that the Stakeholders would have at least read only access there but seems not.
I've invited a new user (external) with Access Level = Stakeholder, given access to the project X and made him a member of Project Contributors for the project.
So the question is, should Stakeholders here have access to the repos? is there a way for me to do this?
If you are using private repos for your project then stakeholders only have access to the following features:
Dashboards, Wiki, Boards, Project and Organization settings - Partial access
Repos, Test Plans - No access
Pipelines, Notifications, Semantic Search - Full access
If you are using public repos for your project then stakeholders only have access to the following features:
Dashboards, Wiki, Boards, Repos, Pipelines, Notifications, Semantic Search - Full access
Test Plans - No access
Project and Organization settings - Partial access
If you want details on Stakeholder access rights for each of the features, go here
I hope that helps.