├── .github ├── CODEOWNERS └── ISSUE_TEMPLATE │ ├── bug_report.md │ └── feature_request.md ├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md └── Teams-repoaccess.ps1 /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | * @vaishnav-canarys 2 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **Screenshots** 14 | If applicable, add screenshots to help explain your problem. 15 | 16 | **Desktop (please complete the following information):** 17 | - OS: [e.g. Windows] 18 | - Powershell Version [e.g. 4.0] 19 | 20 | **Additional context** 21 | Add any other context about the problem here. 22 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: '' 5 | labels: feature 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, sex characteristics, gender identity and expression, 9 | level of experience, education, socio-economic status, nationality, personal 10 | appearance, race, religion, or sexual identity and orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at devopstools@ecanarys.com. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 72 | 73 | [homepage]: https://www.contributor-covenant.org 74 | 75 | For answers to common questions about this code of conduct, see 76 | https://www.contributor-covenant.org/faq 77 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2020 CanarysAutomations 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Automate repo permissions 2 | 3 | ## Overview 4 | 5 | Teams can require access to repositories with different levels of access. The tool with the help of few inputs will **Provide bulk access for teams to the mapped repositories in the excel file**. With each release, the updated exe is available. 6 | 7 | ## Current Challenges 8 | 9 | - When a large number of repositories are migrated to GitHub, we will need to give access to each migrated repo to the relevant team 10 | - The process becomes repititive, when there are 100s of repositories 11 | 12 | ## Benefits 13 | 14 | - The process can be completed in one shot with an excel file which has the repository names, teams and permissions mapped 15 | 16 | ## GitHub REST API 17 | 18 | The endpoints used in the tool are GitHub's Rest API v3. A series of endpoints are made available by GitHub to alter resources like repositories, teams, projects and make organization level changes. For further reading on the GitHub's REST API please [click here](https://docs.github.com/en/free-pro-team@latest/rest/overview) 19 | 20 | ## Prerequisites 21 | 22 | - Only current organizational teams will be considered 23 | - Admin access to the organization for creating the repositories 24 | - Excel File with Team Names and permissions 25 | - GitHub PAT Token must be authorized to access the required organization 26 | 27 | ## Download :arrow_down: 28 | 29 | Download the tool from [here](https://github.com/CanarysAutomations/automate-repository-team-access/releases) 30 | 31 | ## Usage Instructions :memo: 32 | 33 | For instructions on how to use the tool, please [click here](https://github.com/CanarysAutomations/bulk-repository-team-access/wiki) 34 | 35 | ## Current Tool Limitations :x: :x: 36 | 37 | - In the future, GitHub could change its remaining endpoints used in the tool without warning 38 | -------------------------------------------------------------------------------- /Teams-repoaccess.ps1: -------------------------------------------------------------------------------- 1 |  2 | Write-Output " _____ _______ " 3 | Write-Output " | __ \ |__ __| /\ " 4 | Write-Output " | |__) |___ _ __ ___ | | ___ __ _ _ __ ___ ___ / \ ___ ___ ___ ___ ___ " 5 | Write-Output " | _ // _ \ '_ \ / _ \ | |/ _ \/ _ | '_ ` _ \/ __| / /\ \ / __/ __/ _ \/ __/ __| " 6 | Write-Output " | | \ \ __/ |_) | (_) | | | __/ (_| | | | | | \__ \ / ____ \ (_| (_| __/\__ \__ \ " 7 | Write-Output " |_| \_\___| .__/ \___/ |_|\___|\__,_|_| |_| |_|___/ /_/ \_\___\___\___||___/___/ " 8 | Write-Output " | | " 9 | Write-Output " |_| " 10 | Write-Host 11 | 12 | 13 | 14 | 15 | $PATToken = Read-Host -Prompt 'GitHub Token' -AsSecureString 16 | $Organization = Read-Host -Prompt 'GitHub Organization' 17 | $ExcelSourceDir = Read-Host -Prompt 'Excel Source' 18 | $WorkSheetName = Read-Host -Prompt 'Specify the worksheet name' 19 | 20 | 21 | $UserToken =[Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBSTR($PATToken)) 22 | 23 | $head = @{ 24 | 25 | Authorization = 'Bearer ' + $UserToken 26 | Accept ="application/vnd.github.nebula-preview+json" 27 | 28 | } 29 | 30 | $excel = New-Object -com Excel.Application 31 | 32 | $wbook = $excel.workbooks.open($ExcelSourceDir) 33 | 34 | 35 | $worksheet = $wbook.Worksheets.Item($WorkSheetName) 36 | 37 | $maxrows = ($worksheet.UsedRange.Rows).Count 38 | 39 | $wbobject = New-Object -TypeName psobject 40 | $wbobject | Add-Member -MemberType NoteProperty -Name Team -Value $null 41 | $wbobject | Add-Member -MemberType NoteProperty -Name Repository -Value $null 42 | $wbobject | Add-Member -MemberType NoteProperty -Name Permissions -Value $null 43 | 44 | 45 | 46 | for ($i = 2; $i -le $maxrows; $i++) 47 | { 48 | $wbobject.Team = $worksheet.Cells.item($i,1).Text.ToLower(); 49 | $wbobject.Repository = $worksheet.Cells.item($i,2).Text.ToLower(); 50 | $wbobject.Permissions = $worksheet.Cells.item($i,3).Text.ToLower(); 51 | 52 | $repo = $wbobject.Repository 53 | $team = $wbobject.Team 54 | $repopermission = $wbobject.Permissions 55 | 56 | $repoparams=@{ 57 | 58 | permission=$repopermission 59 | 60 | } 61 | 62 | $newteamname = $team -replace ' ','-' 63 | 64 | $body=$repoparams | ConvertTo-Json 65 | 66 | 67 | $teamsaccesstoreposrequest=@{ 68 | 69 | Uri = "https://api.github.com/orgs/$Organization/teams/$newteamname/repos/$Organization/$repo" 70 | Method = "PUT" 71 | body = $body 72 | ContentType = "application/json" 73 | Headers = $head 74 | 75 | } 76 | 77 | try { 78 | 79 | $gitObject= Invoke-RestMethod @teamsaccesstoreposrequest 80 | 81 | $repo_newname= $repo.ToUpper() 82 | $team_newname= $team.ToUpper() 83 | 84 | Write-Host 85 | Write-Host "$team_newname Team has been given $repopermission permissions to $repo_newname" 86 | 87 | } catch{ 88 | 89 | Write-Host "Error:" $_.Exception.Response.StatusDescription -ForegroundColor Red 90 | 91 | } 92 | 93 | } 94 | 95 | 96 | --------------------------------------------------------------------------------