diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index f05727b..e38385d 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,8 +1,14 @@ + + # Summary of changes -Do any of the followings changes break current behaviour or configuration? + -- **YES** / NO +## Breaking Changes + +Do any of the included changes break current behaviour or configuration? + +(**YES** / NO) ## How changes have been tested diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..b468f76 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,72 @@ +# Code of Conduct - github-tag-action + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to make participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, 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. + +## Our Standards + +Examples of behaviour 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 apologising 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 behaviour include: + +* The use of sexualised language or imagery, and sexual attention or + advances +* 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 + +## Our Responsibilities + +Project maintainers are responsible for clarifying and enforcing our standards of +acceptable behaviour and will take appropriate and fair corrective action in +response to any instances of unacceptable behaviour. + +Project maintainers 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, or to ban +temporarily or permanently any contributor for other behaviours that they deem +inappropriate, threatening, offensive, or harmful. + +## 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 behaviour may be +reported to the community leaders responsible for enforcement by logging an issue, +or contacting one or more of the maintainers directly. + +All complaints will be reviewed and investigated to the best of our capacity and ability. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant](https://contributor-covenant.org/), version +[1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct/code_of_conduct.md) and +[2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/code_of_conduct.md), +and was generated by [contributing-gen](https://github.com/bttger/contributing-gen). diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..9537f9f --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,121 @@ + +# Contributing to github-tag-action + +First off, thanks for taking the time to contribute! ❤️ + +All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉 + +> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about: +> +> - Star the project +> - Tweet/Toot/Talk about it +> - Refer this project in your project's readme +> - Mention the project at local meetups and tell your friends/colleagues + + +## Table of Contents + +- [Code of Conduct](#code-of-conduct) +- [I Have a Question](#i-have-a-question) +- [I Want To Contribute](#i-want-to-contribute) + - [Reporting Bugs](#reporting-bugs) + - [Suggesting Enhancements](#suggesting-enhancements) +- [Join The Project Team](#join-the-project-team) + +## Code of Conduct + +This project and everyone participating in it is governed by the +[github-tag-action Code of Conduct](https://github.com/anothrNick/github-tag-actionblob/master/CODE_OF_CONDUCT.md). + +By participating, you are expected to uphold this code. + +## I Have a Question + +> If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/anothrNick/github-tag-action). + +Before you ask a question, it is best to search for existing [Issues](https://github.com/anothrNick/github-tag-action/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first. + +If you then still feel the need to ask a question and need clarification, we recommend the following: + +- Open an [Issue](https://github.com/anothrNick/github-tag-action/issues/new). +- Provide as much context as you can about what you're running into. +- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant. + +We will then take care of the issue as soon as time allows, but please remember this is a community project - we all have our own full time jobs and lives to attend to. + +## I Want To Contribute + +### Legal Notice + +> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license. + +### Reporting Bugs + + +#### Before Submitting a Bug Report + +A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible. + +- Make sure that you are using the latest version. +- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/anothrNick/github-tag-action). If you are looking for support, you might want to check [this section](#i-have-a-question)). +- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/anothrNick/github-tag-actionissues?q=label%3Abug). +- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue. +- Collect information about the bug: + - Logs + - OS, Platform and Version (Windows, Linux, macOS, x86, ARM) + - Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant. + - Possibly your input and the output + - Can you reliably reproduce the issue? And can you also reproduce it with older versions? + + +#### How Do I Submit a Good Bug Report? + +> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <>. + + +We use GitHub issues to track bugs and errors. If you run into an issue with the project: + +- Open an [Issue](https://github.com/anothrNick/github-tag-action/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.) +- Explain the behaviour you would expect and the actual behaviour. +- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case. +- Provide the information you collected in the previous section. + +Once it's filed: + +- The project team will label the issue accordingly. +- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced. +- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution). + + + +### Suggesting Enhancements + +This section guides you through submitting an enhancement suggestion for github-tag-action, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions. + + +#### Before Submitting an Enhancement + +- Make sure that you are using the latest version. +- Read the [documentation](https://github.com/anothrNick/github-tag-action) carefully and find out if the functionality is already covered, maybe by an individual configuration. +- Perform a [search](https://github.com/anothrNick/github-tag-action/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one. +- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library. + + +#### How Do I Submit a Good Enhancement Suggestion? + +Enhancement suggestions are tracked as [GitHub issues](https://github.com/anothrNick/github-tag-action/issues). + +- Use a **clear and descriptive title** for the issue to identify the suggestion. +- Provide a **step-by-step description of the suggested enhancement** in as many details as possible. +- **Describe the current behaviour** and **explain which behaviour you expected to see instead** and why. At this point you can also tell which alternatives do not work for you. +- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. +- **Explain why this enhancement would be useful** to most github-tag-action users. You may also want to point out the other projects that solved it better and which could serve as inspiration. + +## Join The Project Team + +- 📣 [This project is supported by the community and seeking maintainers!](https://github.com/anothrNick/github-tag-action/issues/238) + + +## Attribution + +This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)! diff --git a/LICENSE b/LICENSE index 0b6d33a..4f5eb3f 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2019 Nick +Copyright (c) 2023 Nick Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal @@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. \ No newline at end of file +SOFTWARE. diff --git a/README.md b/README.md index 9713c79..605dcf7 100755 --- a/README.md +++ b/README.md @@ -10,7 +10,11 @@ A Github Action to automatically bump and tag master, on merge, with the latest [](https://itnext.io/creating-a-github-action-to-tag-commits-2722f1560dec) -### Usage +> 📣 [This project seeking maintainers!](https://github.com/anothrNick/github-tag-action/issues/238) 📣 + +## Usage + +_Note: We don't recommend using the @master version unless you're happy to test the latest changes._ ```yaml # example 1: on push to master @@ -28,7 +32,7 @@ jobs: fetch-depth: '0' - name: Bump version and push tag - uses: anothrNick/github-tag-action@v1 + uses: anothrNick/github-tag-action@1.55.0 # Don't use @master unless you're happy to test the latest version env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} WITH_V: true @@ -53,17 +57,19 @@ jobs: fetch-depth: '0' - name: Bump version and push tag - uses: anothrNick/github-tag-action@v1 + uses: anothrNick/github-tag-action@1.55.0 # Don't use @master unless you're happy to test the latest version env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} WITH_V: true ``` -**Depending if you choose example 1 or example 2 is how crafted version bumps operate when reading the commit log. Is recommended to use on `pull_request` instead of on commit to master/main.** +Depending if you choose example 1 or example 2 is how crafted version bumps operate when reading the commit log. + +Is recommended to use on `pull_request` instead of on commit to master/main. _NOTE: set the fetch-depth for `actions/checkout@v2` or newer to be sure you retrieve all commits to look for the semver commit message._ -#### Options +### Options **Environment Variables** @@ -89,7 +95,7 @@ _NOTE: set the fetch-depth for `actions/checkout@v2` or newer to be sure you ret - `last`: show the single last commit - `compare`: show all commits since previous repo tag number -#### Outputs +### Outputs - **new_tag** - The value of the newly created tag. - **tag** - The value of the latest tag after running this action. @@ -118,16 +124,20 @@ If `#none` is contained in the merge commit message, it will skip bumping regard - If triggered on your repo's default branch (`master` or `main` if unchanged), the bump version will be a release tag. - If triggered on any other branch, a prerelease will be generated, depending on the bump, starting with `*-.1`, `*-.2`, ... -### Credits +## Contributing -[fsaintjacques/semver-tool](https://github.com/fsaintjacques/semver-tool) +See [CONTRIBUTING.md](CONTRIBUTING.md) and [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md). -### Projects using github-tag-action +## Credits -A list of projects using github-tag-action for reference. +- [fsaintjacques/semver-tool](https://github.com/fsaintjacques/semver-tool) +- [Contributors to this project](https://github.com/anothrNick/github-tag-action/graphs/contributors) -- another/github-tag-action (uses itself to create tags) +## Projects using github-tag-action + +Examples of projects using github-tag-action for reference. +- another/github-tag-action (uses itself to create tags) - [anothrNick/json-tree-service](https://github.com/anothrNick/json-tree-service) > Access JSON structure with HTTP path parameters as keys/indices to the JSON.