Skip to content

Commit ccccbc0

Browse files
gep13gep13
committed
Merge branch 'release/5.1.0'
* release/5.1.0: (GH-113) Add standard AppVeyor Config file (GH-113) Add EditorConfig file (GH-113) Add GitHub Template files (GH-113) Correct license expression (GH-113) Update NuGet metadata (GH-113) Always run GitVersion (GH-113) Pin to 1.0.0 of Cake.Recipe (GH-113) Switch to recipe.cake file (GH-113) Update to latest Cake bootstrappers Fix package icon
2 parents 5155ba4 + ceb7130 commit ccccbc0

11 files changed

+438
-67
lines changed

‎.appveyor.yml

+24-8
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,30 @@
1+
#---------------------------------#
2+
# Build Image #
3+
#---------------------------------#
4+
image: Visual Studio 2017
5+
16
#---------------------------------#
27
# Build Script #
38
#---------------------------------#
49
build_script:
5-
- ps: .\build.ps1 -Target AppVeyor
6-
10+
- ps: .\build.ps1 -Target AppVeyor
711

12+
#---------------------------------#
813
# Tests
14+
#---------------------------------#
915
test: off
1016

17+
#---------------------------------#
18+
# Pull Requests #
19+
#---------------------------------#
20+
pull_requests:
21+
do_not_increment_build_number: true
22+
23+
#---------------------------------#
24+
# General #
25+
#---------------------------------#
26+
skip_branch_with_pr: true
27+
1128
#---------------------------------#
1229
# Branches to build #
1330
#---------------------------------#
@@ -23,12 +40,11 @@ branches:
2340
# Build Cache #
2441
#---------------------------------#
2542
cache:
26-
- src\packages -> src\**\packages.config
27-
#- tools -> setup.cake
43+
- tools -> recipe.cake, tools/packages.config
2844

2945
#---------------------------------#
30-
# environment configuration #
46+
# Skip builds for doc changes #
3147
#---------------------------------#
32-
33-
# Build worker image (VM template)
34-
image: Visual Studio 2017
48+
skip_commits:
49+
# Regex for matching commit message
50+
message: /(doc).*/

‎.editorconfig

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
; This file is for unifying the coding style for different editors and IDEs.
2+
; More information at http://EditorConfig.org
3+
4+
root = true
5+
6+
[*]
7+
end_of_line = CRLF
8+
9+
[*.ps1]
10+
indent_style = space
11+
indent_size = 4
12+
13+
[*.cs]
14+
indent_style = space
15+
indent_size = 4
16+
17+
[*.cake]
18+
indent_style = space
19+
indent_size = 4
20+
21+
[*.js]
22+
indent_style = tab
23+
indent_size = 2

‎.github/CODEOFCONDUCT.md

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# Contributor Code of Conduct
2+
3+
As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
4+
5+
We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
6+
7+
Examples of unacceptable behavior by participants include:
8+
9+
- The use of sexualized language or imagery
10+
- Personal attacks
11+
- Trolling or insulting/derogatory comments
12+
- Public or private harassment
13+
- Publishing other's private information, such as physical or electronic addresses, without explicit permission
14+
- Other unethical or unprofessional conduct
15+
16+
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.
17+
18+
By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team.
19+
20+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
21+
22+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a project maintainer at [abuse@gep13.co.uk](mailto:abuse@gep13.co.uk). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Maintainers are obligated to maintain confidentiality with regard to the reporter of an incident.
23+
24+
This Code of Conduct is adapted from the Contributor Covenant, version 1.3.0, available from http://contributor-covenant.org/version/1/3/0/

‎.github/CONTRIBUTING.md

+51
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
# How to contribute
2+
Contributions to Cake.Incubator are highly encouraged and desired. Below are some guidelines that will help make the process as smooth as possible.
3+
4+
# Getting Started
5+
* Make sure you have a [GitHub account](https://github.com/signup/free)
6+
* Submit a new issue, assuming one does not already exist.
7+
* Clearly describe the issue including steps to reproduce when it is a bug.
8+
* Make sure you fill in the earliest version that you know has the issue.
9+
* Fork the repository on GitHub
10+
11+
# Suggesting Enhancements
12+
We want to know what you think is missing from Cake.Incubator and how it can be made better.
13+
* When submitting an issue for an enhancement, please be as clear as possible about why you think the enhancement is needed and what the benefit of
14+
it would be.
15+
16+
# Making Changes
17+
* From your fork of the repository, create a topic branch where work on your change will take place.
18+
* To quickly create a topic branch based on master; `git checkout -b my_contribution master`. Please avoid working directly on the `master` branch.
19+
* Make commits of logical units.
20+
* Check for unnecessary whitespace with `git diff --check` before committing.
21+
* Please follow the prevailing code conventions in the repository. Differences in style make the code harder to understand for everyone.
22+
* Make sure your commit messages are in the proper format.
23+
````
24+
Add more cowbell to Get-Something.ps1
25+
26+
The functionaly of Get-Something would be greatly improved if there was a little
27+
more 'pizzazz' added to it. I propose a cowbell. Adding more cowbell has been
28+
shown in studies to both increase one's mojo, and cement one's status
29+
as a rock legend.
30+
````
31+
32+
* Make sure you have added all the necessary Pester tests for your changes.
33+
* Run _all_ PESTER tests in the module to assure nothing else was accidentally broken.
34+
35+
# Documentation
36+
We are infallible and as such the documenation needs no corectoin. In the highly
37+
unlikely event that that is _not_ the case, commits to update or add documentation
38+
are highly apprecaited.
39+
40+
# Submitting Changes
41+
* Push your changes to a topic branch in your fork of the repository.
42+
* Submit a pull request to the main repository.
43+
* Once the pull request has been reviewed and accepted, it will be merged with the master branch.
44+
* Celebrate
45+
46+
# Additional Resources
47+
* [General GitHub documentation](https://help.github.com/)
48+
* [GitHub forking documentation](https://guides.github.com/activities/forking/)
49+
* [GitHub pull request documentation](https://help.github.com/send-pull-requests/)
50+
* [GitHub Flow guide](https://guides.github.com/introduction/flow/)
51+
* [GitHub's guide to contributing to open source projects](https://guides.github.com/activities/contributing-to-open-source/)

‎.github/ISSUE_TEMPLATE.md

+30
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
<!--- Provide a general summary of the issue in the Title above -->
2+
3+
## Expected Behavior
4+
<!--- If you're describing a bug, tell us what should happen -->
5+
<!--- If you're suggesting a change/improvement, tell us how it should work -->
6+
7+
## Current Behavior
8+
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
9+
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
10+
11+
## Possible Solution
12+
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
13+
<!--- or ideas how to implement the addition or change -->
14+
15+
## Steps to Reproduce (for bugs)
16+
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
17+
<!--- reproduce this bug. Include code to reproduce, if relevant -->
18+
1.
19+
2.
20+
3.
21+
4.
22+
23+
## Context
24+
<!--- How has this issue affected you? What are you trying to accomplish? -->
25+
<!--- Providing context helps us come up with a solution that is most useful in the real world -->
26+
27+
## Your Environment
28+
<!--- Include as many relevant details about the environment you experienced the bug in -->
29+
* Module version used:
30+
* Operating System and PowerShell version:

‎.github/PULL_REQUEST_TEMPLATE.md

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
<!--- Provide a general summary of your changes in the Title above -->
2+
3+
## Description
4+
<!--- Describe your changes in detail -->
5+
6+
## Related Issue
7+
<!--- This project only accepts pull requests related to open issues -->
8+
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
9+
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
10+
<!--- Please link to the issue here: -->
11+
12+
## Motivation and Context
13+
<!--- Why is this change required? What problem does it solve? -->
14+
15+
## How Has This Been Tested?
16+
<!--- Please describe in detail how you tested your changes. -->
17+
<!--- Include details of your testing environment, and the tests you ran to -->
18+
<!--- see how your change affects other areas of the code, etc. -->
19+
20+
## Screenshots (if appropriate):
21+
22+
## Types of changes
23+
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
24+
- [ ] Bug fix (non-breaking change which fixes an issue)
25+
- [ ] New feature (non-breaking change which adds functionality)
26+
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
27+
28+
## Checklist:
29+
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
30+
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
31+
- [ ] My code follows the code style of this project.
32+
- [ ] My change requires a change to the documentation.
33+
- [ ] I have updated the documentation accordingly.
34+
- [ ] I have read the **CONTRIBUTING** document.
35+
- [ ] I have added tests to cover my changes.
36+
- [ ] All new and existing tests passed.

0 commit comments

Comments
 (0)