Skip to content
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.

Commit

Permalink
fix: update settings and codeowners
Browse files Browse the repository at this point in the history
  • Loading branch information
mike-audi committed May 14, 2024
1 parent 19935d1 commit 4bc44bd
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 55 deletions.
2 changes: 1 addition & 1 deletion .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
Expand Up @@ -3,4 +3,4 @@
# @org/team will be requested for review when someone opens
# a pull request. Order is important; the last matching
# pattern takes the most precedence.
#* @org/team
* @tiki-bar/sysadmin
76 changes: 22 additions & 54 deletions .github/settings.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,61 +3,29 @@
_extends: .github

repository:
# # The name of the repository. Changing this will rename the repository
# name: repo-name
#
# # A short description of the repository that will show up on GitHub
# description: description of repo
#
# # A URL with more information about the repository
# homepage: https://example.github.io/
#
# # A comma-separated list of topics to set on the repository
# topics: github, probot
#
# # Either `true` to make the repository private, or `false` to make it public.
# private: false

name: sar-template
description: Publish and share Organization wide Cloudformation templates using the Serverless Application Repository (SAR).
topics: aws, sar, example
private: false
has_issues: true
has_projects: true
has_discussions: false

#teams:
# - name: core
# permission: admin

#collaborators:
# - username: bkeepers
# permission: push

# The permission to grant:
# * `pull` - can pull, but not push to or administer this repository.
# * `push` - can pull and push, but not administer this repository.
# * `admin` - can pull, push and administer this repository.
# * `maintain` - Recommended for project managers who need to manage the repository without access to sensitive or destructive actions.
# * `triage` - Recommended for contributors who need to proactively manage issues and pull requests without write access.

#environments:
# - name: production
# reviewers:
# - id: 1
# type: 'Team'

#branches:
# - name: main
# protection:
# required_status_checks:
# strict: true
# # Required. The list of status checks to require in order to merge into this branch
# contexts: []

#labels:
# - name: breaking
# color: D73A4A
# description: Introduces a breaking change.

#milestones:
# - title: milestone-title
# description: milestone-description
# # The state of the milestone. Either `open` or `closed`
# state: open
teams:
- name: sysadmin
permission: admin
- name: engineering
permission: push
- name: product
permission: triage

environments:
- name: production

branches:
- name: main
protection:
required_status_checks:
strict: true
contexts:
- Test

0 comments on commit 4bc44bd

Please sign in to comment.