From 40ca351febfd2a6ae742574b289b3acbd80e8d93 Mon Sep 17 00:00:00 2001 From: Predrag Gruevski <2348618+obi1kenobi@users.noreply.github.com> Date: Sun, 7 Aug 2022 22:10:06 -0400 Subject: [PATCH 1/3] Mark the README code blocks as YAML. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 50f386e..fc30a70 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ By default, this action assumes that: - Your releases are tagged in git as `v{major}.{minor}.{patch}`, for example `v1.2.3`. Single-crate workspaces can use it as: -``` +```yaml - name: Check semver uses: obi1kenobi/cargo-semver-checks-action@v1 - name: Publish to crates.io @@ -18,7 +18,7 @@ In a workspace with more than one crate: - use the `version-tag-prefix` setting to override the default prefix `v` to match the way the releases of your crate are tagged. The version number `1.2.3` will be appended to this prefix. For example, this is publishing `my-crate` whose releases are tagged as `my-crate-v1.2.3`: -``` +```yaml - name: Check semver uses: obi1kenobi/cargo-semver-checks-action@v1 with: @@ -29,7 +29,7 @@ For example, this is publishing `my-crate` whose releases are tagged as `my-crat ``` To check a different (non-library) target in a crate, use the `crate-target` setting: -``` +```yaml - name: Check semver for my_binary uses: obi1kenobi/cargo-semver-checks-action@v1 with: From 29d1ccab21a26a81ca59f18c43df2bc0d9ce7ba4 Mon Sep 17 00:00:00 2001 From: Ed Page Date: Tue, 9 Aug 2022 11:50:33 -0500 Subject: [PATCH 2/3] chore(gh): Allow contributors to update repo settings --- .github/settings.yml | 45 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 .github/settings.yml diff --git a/.github/settings.yml b/.github/settings.yml new file mode 100644 index 0000000..b9c23ee --- /dev/null +++ b/.github/settings.yml @@ -0,0 +1,45 @@ +# These settings are synced to GitHub by https://probot.github.io/apps/settings/ + +repository: + description: A GitHub Action for running cargo-semver-checks + topics: rust cargo semver action + has_issues: true + has_projects: true + has_wiki: true + has_downloads: true + default_branch: main + + allow_squash_merge: true + allow_merge_commit: true + allow_rebase_merge: true + + allow_auto_merge: true + delete_branch_on_merge: true + +labels: + - name: A-action + color: '#f7e101' + description: "Area: the action itself" + - name: A-docs + color: '#f7e101' + description: "Area: documentation for the command and lints" + - name: C-bug + color: '#b60205' + description: "Category: doesn't meet expectations" + - name: C-enhancement + color: '#1d76db' + description: "Category: raise the bar on expectations" + - name: M-breaking-change + color: "#E10C02" + description: "Meta: Implementing or merging this will introduce a breaking change." + - name: E-help-wanted + color: '#02E10C' + description: "Call for participation: Help is requested to fix this issue." + +branches: + - name: main + protection: + required_pull_request_reviews: null + required_conversation_resolution: true + enforce_admins: false + restrictions: null From a70dd5d8675074e37f66b002e5a77e4d01a4087e Mon Sep 17 00:00:00 2001 From: Predrag Gruevski <2348618+obi1kenobi@users.noreply.github.com> Date: Wed, 10 Aug 2022 01:28:06 -0400 Subject: [PATCH 3/3] Add branding info to action. --- action.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/action.yml b/action.yml index dd384ef..ff00f1d 100644 --- a/action.yml +++ b/action.yml @@ -1,5 +1,8 @@ name: 'cargo-semver-checks' description: 'Ensure the public API in your Rust crate follows semantic versioning' +branding: + icon: 'check-circle' + color: 'green' inputs: crate-name: description: 'The crate whose API to check for semver'