settings

Open
#7 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github
Domain
devops

Research direction

Start by surveying existing organization and repository settings patterns, then review how probot/settings and CODEOWNERS would apply to the proposed defaults. Done means the required org defaults, per-repository settings, team permissions, labels, and owner-review policy are agreed and documented.

Written by the indexing model from the issue text.

Description

to prepare for configuring https://github.com/probot/settings for this org, i thought i'd start by capturing thoughts here. i'll work to survey existing patterns, but feel free to comment if i've missed things that we want to make sure to capture or if there are specific defaults that we should target.

Settings

Org defaults
  • repo details
    • allowed merge strategies
    • wikis/projects/downloads
  • branch protection
  • team permissions
  • labels? (this gets a little clunky once certain repos need additional labels beyond the defaults)
Per repo details
  • name
  • description
  • homepage
  • visibility
  • team permissions when different than defaults
  • additional collaborators? (i'd prefer to define teams if the need for this exists)

Security

since having access to modify the settings file effectively elevates someone to admin, it may be worth requiring owner review through CODEOWNERS. currently the maintainers team is essentially the same as owners. do we want that to stay that way. especially since the bot currently does not push updates to all repos after updating the org level file, would it be worth creating an owners team for this now, even if it has the same members?

Dominant language
No language data
Stars
6
Forks
5
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from semantic-release/.github

All issues in semantic-release/.github

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.