-
Notifications
You must be signed in to change notification settings - Fork 848
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2175 from Varying-Vagrant-Vagrants/develop
3.4.1 release
- Loading branch information
Showing
35 changed files
with
1,496 additions
and
878 deletions.
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,76 @@ | ||
| # Contributor Covenant Code of Conduct | ||
|
|
||
| ## Our Pledge | ||
|
|
||
| In the interest of fostering an open and welcoming environment, we as | ||
| contributors and maintainers pledge to making 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 behavior that contributes to creating a positive environment | ||
| include: | ||
|
|
||
| * Using welcoming and inclusive language | ||
| * Being respectful of differing viewpoints and experiences | ||
| * Gracefully accepting constructive criticism | ||
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
|
|
||
| Examples of unacceptable behavior by participants include: | ||
|
|
||
| * The use of sexualized language or imagery and unwelcome sexual attention or | ||
| advances | ||
| * Trolling, insulting/derogatory comments, and personal or political attacks | ||
| * Public or private harassment | ||
| * Publishing others' private information, such as a physical or electronic | ||
| address, without explicit permission | ||
| * Other conduct which could reasonably be considered inappropriate in a | ||
| professional setting | ||
|
|
||
| ## Our Responsibilities | ||
|
|
||
| Project maintainers are responsible for clarifying the standards of acceptable | ||
| behavior and are expected to take appropriate and fair corrective action in | ||
| response to any instances of unacceptable behavior. | ||
|
|
||
| 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 behaviors that they deem inappropriate, | ||
| threatening, offensive, or harmful. | ||
|
|
||
| ## Scope | ||
|
|
||
| This Code of Conduct applies both within project spaces and in public spaces | ||
| when an individual is representing the project or its community. Examples of | ||
| representing a project or community include using an official project e-mail | ||
| address, posting via an official social media account, or acting as an appointed | ||
| representative at an online or offline event. Representation of a project may be | ||
| further defined and clarified by project maintainers. | ||
|
|
||
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported by contacting the project team at [email protected]. All | ||
| complaints will be reviewed and investigated and will result in a response that | ||
| is deemed necessary and appropriate to the circumstances. The project team is | ||
| obligated to maintain confidentiality with regard to the reporter of an incident. | ||
| Further details of specific enforcement policies may be posted separately. | ||
|
|
||
| Project maintainers who do not follow or enforce the Code of Conduct in good | ||
| faith may face temporary or permanent repercussions as determined by other | ||
| members of the project's leadership. | ||
|
|
||
| ## Attribution | ||
|
|
||
| This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, | ||
| available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html | ||
|
|
||
| [homepage]: https://www.contributor-covenant.org | ||
|
|
||
| For answers to common questions about this code of conduct, see | ||
| https://www.contributor-covenant.org/faq |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,67 @@ | ||
| # Configuration for update-docs - https://github.com/behaviorbot/update-docs | ||
|
|
||
| # Comment to be posted to on PRs that don't update documentation | ||
| updateDocsComment: > | ||
| Thanks for opening this pull request! Make sure `CHANGELOG.md` gets updated with this change, additionally any docs that need updated can be found at https://github.com/Varying-Vagrant-Vagrants/varyingvagrantvagrants.org | ||
| targetFiles: | ||
| - CHANGELOG.md | ||
|
|
||
| # Comment to be posted to on first time issues | ||
| newIssueWelcomeComment: > | ||
| Thanks for opening your first issue here! Be sure to follow the issue template and include your OS/Vagrant/VVV versions! Don't forget you can get support in the VVV slack at https://varyingvagrantvagrants.org/docs/en-US/slack/ | ||
| # Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome | ||
|
|
||
| # Comment to be posted to on PRs from first time contributors in your repository | ||
| newPRWelcomeComment: false | ||
|
|
||
| # Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge | ||
|
|
||
| # Comment to be posted to on pull requests merged by a first time user | ||
| firstPRMergeComment: > | ||
| Congrats on merging your first pull request! | ||
| # Configuration for request-info - https://github.com/behaviorbot/request-info | ||
|
|
||
| # *OPTIONAL* Comment to reply with | ||
| # Can be either a string : | ||
| requestInfoReplyComment: > | ||
| Thanks for contributing, it would be a help if you can provide us with more info! | ||
| # Or an array: | ||
| # requestInfoReplyComment: | ||
| # - Ah no! young blade! That was a trifle short! | ||
| # - Tell me more ! | ||
| # - I am sure you can be more effusive | ||
|
|
||
|
|
||
| # *OPTIONAL* default titles to check against for lack of descriptiveness | ||
| # MUST BE ALL LOWERCASE | ||
| requestInfoDefaultTitles: | ||
| - update readme.md | ||
| - updates | ||
|
|
||
| # *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given | ||
| requestInfoLabelToAdd: needs-more-info | ||
|
|
||
| # *OPTIONAL* Require Issues to contain more information than what is provided in the issue templates | ||
| # Will fail if the issue's body is equal to a provided template | ||
| checkIssueTemplate: true | ||
|
|
||
| # *OPTIONAL* Require Pull Requests to contain more information than what is provided in the PR template | ||
| # Will fail if the pull request's body is equal to the provided template | ||
| checkPullRequestTemplate: true | ||
|
|
||
| # *OPTIONAL* Only warn about insufficient information on these events type | ||
| # Keys must be lowercase. Valid values are 'issue' and 'pullRequest' | ||
| requestInfoOn: | ||
| pullRequest: true | ||
| issue: true | ||
|
|
||
| # *OPTIONAL* Add a list of people whose Issues/PRs will not be commented on | ||
| # keys must be GitHub usernames | ||
| requestInfoUserstoExclude: | ||
| - hiimbex | ||
| - bexo |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| # Configuration for Lock Threads - https://github.com/dessant/lock-threads-app | ||
|
|
||
| # Number of days of inactivity before a closed issue or pull request is locked | ||
| daysUntilLock: 20 | ||
|
|
||
| # Skip issues and pull requests created before a given timestamp. Timestamp must | ||
| # follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable | ||
| skipCreatedBefore: false | ||
|
|
||
| # Issues and pull requests with these labels will be ignored. Set to `[]` to disable | ||
| exemptLabels: [] | ||
|
|
||
| # Label to add before locking, such as `outdated`. Set to `false` to disable | ||
| lockLabel: false | ||
|
|
||
| # Comment to post before locking. Set to `false` to disable | ||
| lockComment: > | ||
| This thread has been automatically locked since there has not been | ||
| any recent activity after it was closed. Please open a new issue for | ||
| related bugs. | ||
| # Assign `resolved` as the reason for locking. Set to `false` to disable | ||
| setLockReason: false | ||
|
|
||
| # Limit to only `issues` or `pulls` | ||
| only: issues | ||
|
|
||
| # Optionally, specify configuration settings just for `issues` or `pulls` | ||
| # issues: | ||
| # exemptLabels: | ||
| # - help-wanted | ||
| # lockLabel: outdated | ||
|
|
||
| # pulls: | ||
| # daysUntilLock: 30 | ||
|
|
||
| # Repository to extend settings from | ||
| # _extends: repo |
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
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
Oops, something went wrong.