Fix readme #630
Merged
Fix readme #630
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MaksimZhukov
approved these changes
Jul 31, 2023
dmitry-shibanov
approved these changes
Jul 31, 2023
IvanZosimov
approved these changes
Jul 31, 2023
|
@sungh0lim thank you for the pull request! |
|
@MaksimZhukov Glad to be able to contribute! If there's any issue that I can contribute, I'd love to try. |
sp3nx0r
pushed a commit
to sp3nx0r/homelab
that referenced
this pull request
Dec 24, 2023
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [actions/labeler](https://togithub.com/actions/labeler) | action | major | `v4.3.0` -> `v5.0.0` | --- ### Release Notes <details> <summary>actions/labeler (actions/labeler)</summary> ### [`v5.0.0`](https://togithub.com/actions/labeler/releases/tag/v5.0.0) [Compare Source](https://togithub.com/actions/labeler/compare/v4.3.0...v5.0.0) #### What's Changed This release contains the following breaking changes: 1. The ability to apply labels based on the names of base and/or head branches was added ([#​186](https://togithub.com/actions/labeler/issues/186) and [#​54](https://togithub.com/actions/labeler/issues/54)). The match object for changed files was expanded with new combinations in order to make it more intuitive and flexible ([#​423](https://togithub.com/actions/labeler/issues/423) and [#​101](https://togithub.com/actions/labeler/issues/101)). As a result, the configuration file structure was significantly redesigned and is not compatible with the structure of the previous version. Please read the [action documentation](https://togithub.com/actions/labeler/tree/main#pull-request-labeler) to find out how to adapt your configuration files for use with the new action version. 2. The bug related to the `sync-labels` input was fixed ([#​112](https://togithub.com/actions/labeler/issues/112)). Now the input value is read correctly. 3. By default, `dot` input is set to `true`. Now, paths starting with a dot (e.g. `.github`) are matched by default. 4. Version 5 of this action updated the [runtime to Node.js 20](https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions). All scripts are now run with Node.js 20 instead of Node.js 16 and are affected by any breaking changes between Node.js 16 and 20. For more information, please read the [action documentation](https://togithub.com/actions/labeler/tree/main#pull-request-labeler). #### New Contributors - [@​joshdales](https://togithub.com/joshdales) made their first contribution in [actions/labeler#203 - [@​dusan-trickovic](https://togithub.com/dusan-trickovic) made their first contribution in [actions/labeler#626 - [@​sungh0lim](https://togithub.com/sungh0lim) made their first contribution in [actions/labeler#630 - [@​TrianguloY](https://togithub.com/TrianguloY) made their first contribution in [actions/labeler#629 **Full Changelog**: actions/labeler@v4...v5.0.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/sp3nx0r/homelab). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy44Ny4yIiwidXBkYXRlZEluVmVyIjoiMzcuODcuMiIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
](https://renovatebot.com){kind=link}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
jobs > triagein the workflow in the README.md file. because it was different in each example.Related issue:
Add link to the related issue.
Check list: