Skip to content

Commit

Permalink
feat: created a shared renovate config
Browse files Browse the repository at this point in the history
  • Loading branch information
prisis committed Nov 2, 2023
1 parent c5c156d commit b21e7d7
Show file tree
Hide file tree
Showing 44 changed files with 12,658 additions and 2 deletions.
1 change: 1 addition & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
/.yarn/** linguist-vendored
1 change: 1 addition & 0 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* @prisis
84 changes: 84 additions & 0 deletions .github/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@
# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our community include:

- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

- The use of sexualized language or imagery, and sexual attention or
advances of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email
address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a
professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [[email protected]](mailto:[email protected]). All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series of actions.

**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
Empty file added .github/CONTRIBUTING.md
Empty file.
1 change: 1 addition & 0 deletions .github/FUNDING.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
github: "prisis"
9 changes: 9 additions & 0 deletions .github/file-filters.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
This is used by the action https://github.com/dorny/paths-filter (which we have forked to https://github.com/getsentry/paths-filter)

markdown_lintable:
- "**/*.md"
- "**/*.mdx"

yaml_lintable:
- "**/*.yml"
- "**/*.yaml"
19 changes: 19 additions & 0 deletions .github/semantic.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# In order to let this correctly work, install https://github.com/apps/semantic-pull-requests

titleOnly: true
types:
- "feat"
- "fix"
- "docs"
- "dx"
- "refactor"
- "perf"
- "test"
- "workflow"
- "build"
- "ci"
- "chore"
- "types"
- "wip"
- "release"
- "deps"
182 changes: 182 additions & 0 deletions .github/settings.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,182 @@
# https://github.com/probot/settings

branches:
- name: "main"

# https://docs.github.com/en/rest/reference/repos#delete-branch-protection
# https://docs.github.com/en/rest/reference/repos#update-branch-protection

protection:
enforce_admins: false

required_pull_request_reviews:
dismiss_stale_reviews: true
require_code_owner_reviews: true
required_approving_review_count: 1

required_status_checks:
contexts: []

strict: false

restrictions:
# https://developer.github.com/v3/repos/branches/#parameters-1

# Note: User, app, and team restrictions are only available for organization-owned repositories.
# Set to null to disable when using this configuration for a repository on a personal account.

apps:
- "semantic-release-bot"
- "renovate"
teams: []
# users: []

# https://docs.github.com/en/rest/reference/issues#create-a-label
# https://docs.github.com/en/rest/reference/issues#update-a-label

labels:
- name: "s: needs decision"
description: "Needs team/maintainer decision"
color: "C453C3"

- name: "s: needs proposal"
description: "Changelog Fixed"
color: "fbca04"

- name: "s: needs design"
description: "Changelog Fixed"
color: "fbca04"

- name: "s: accepted"
description: "Accepted feature / Confirmed bug"
color: "0E8A16"

- name: "s: awaiting more info"
description: "Additional information are requested"
color: "B76026"

- name: "s: invalid"
description: "This doesn't seem right"
color: "E4E669"

- name: "s: on hold"
description: "Blocked by something or frozen to avoid conflicts"
color: "A03F0B"

- name: "s: pending triage"
description: "Pending Triage"
color: "dddddd"

- name: "s: waiting for user interest"
description: "Waiting for more users interested in this feature"
color: "4B02CE"

- name: "wontfix"
description: "This will not be worked on"
color: "ffffff"

- name: "question"
description: "Further information is requested"
color: "956692"

- name: "p: 1-normal"
description: "Nothing urgent"
color: "BFDADC"

- name: "p: 2-high"
description: "Fix main branch"
color: "FF4d4d"

- name: "p: 3-urgent"
description: "Fix and release ASAP"
color: "FF0000"

- name: "needs test"
description: "More tests are needed"
color: "FAF1A2"

- name: "needs rebase"
description: "There is a merge conflict"
color: "32345B"

- name: "c: bug"
description: "Something isn't working"
color: "FFA500"

- name: "c: chore"
description: "PR that doesn't affect the runtime behavior"
color: "40E0D0"

- name: "c: docs"
description: "Improvements or additions to documentation"
color: "FFFF00"

- name: "c: dependencies"
description: "Pull requests that adds/updates a dependency"
color: "AFEEEE"

- name: "c: feature"
description: "Request for new feature"
color: "2878FF"

- name: "c: infra"
description: "Changes to our infrastructure or project setup"
color: "2c3e50"

- name: "c: refactor"
description: "PR that affects the runtime behavior, but doesn't add new features or fixes bugs"
color: "40E0D0"

- name: "c: security"
description: "Indicates a vulnarability"
color: "B60205"

- name: "deprecation"
description: "A deprecation was made in the PR"
color: "C5DEF5"

- name: "do NOT merge yet"
description: "Do not merge this PR into the target branch yet"
color: "FF0205"

- name: "duplicate"
description: "Duplicate of another issue/PR"
color: "fef2c0"

- name: "good first issue"
description: "Good for newcomers"
color: "7057ff"

- name: "has workaround"
description: "Workaround provided or linked"
color: "4049AD"

- name: "help wanted"
description: "Extra attention is needed"
color: "008672"

- name: "breaking change"
description: "Cannot be merged when next version is not a major release"
color: "B05D08"

# https://docs.github.com/en/rest/reference/repos#update-a-repository

repository:
allow_merge_commit: true
allow_rebase_merge: false
allow_squash_merge: false
archived: false
default_branch: "main"
delete_branch_on_merge: true
description: "Shareable config for Renovate (renovatebot.com)"
has_downloads: true
has_issues: true
has_pages: false
has_projects: false
has_wiki: false
name: "renovate-config"
private: false

# https://developer.github.com/v3/repos/branches/#remove-branch-protection

topics: "renovate renovate-config anolilab javascript github actions github-actions preset"
39 changes: 39 additions & 0 deletions .github/workflows/cache-clear.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
name: "cleanup caches by a branch"

on: # yamllint disable-line rule:truthy
pull_request:
types:
- "closed"

jobs:
cleanup:
runs-on: "ubuntu-latest"
steps:
- name: "Harden Runner"
uses: "step-security/harden-runner@1b05615854632b887b69ae1be8cbefe72d3ae423" # v2.6.0
with:
egress-policy: "audit"

- name: "Check out code"
uses: "actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11" # v4.1.1

- name: "Cleanup"
run: |
gh extension install actions/gh-actions-cache
REPO=${{ github.repository }}
BRANCH="refs/pull/${{ github.event.pull_request.number }}/merge"
echo "Fetching list of cache key"
cacheKeysForPR=$(gh actions-cache list -R $REPO -B $BRANCH | cut -f 1 )
## Setting this to not fail the workflow while deleting cache keys.
set +e
echo "Deleting caches..."
for cacheKey in $cacheKeysForPR
do
gh actions-cache delete $cacheKey -R $REPO -B $BRANCH --confirm
done
echo "Done"
env:
GH_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
Loading

0 comments on commit b21e7d7

Please sign in to comment.