You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(functions): 🚑 Login check did not work. PAT was always used
feat(functions): Added a way to function to clear authentication header
refactor: 🚚 Moving all the functions in different folders
feat: Added function for branch control on pipeline
feat(workflow): Added psscriptanalyzer
chore(release): v0.1.0 [skip ci]
fix(worklows): 🚀 Added repo parameter
chore(release): v0.2.0 [skip ci]
chore(release): v0.3.0 [skip ci]
chore(release): v0.4.0 [skip ci]
fix: 🚀 Fixing psgallery Api key
fix: 🚀 Added build task to psake
feat: adding version to publish
fix: typo
fix: changed to publish-module
fix: Added update-modulemanifest
fix: typo
fix: -as [version]
fix: changed to init
fix: typo
fix:typo
fix: removed cast
fix: testing build
fix: Switch order
fix: replaced path
fix: update manifest
fix: added functionsToExport to workflow
fix: testing version from tripss action
fix: fixed version
fix: typo
fix: testing new github release
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+12-17Lines changed: 12 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,52 +5,48 @@ Below are some guidelines that will help make the process as smooth as possible.
5
5
6
6
## Getting Started
7
7
8
-
- Make sure you have a [GitHub account](https://github.com/signup/free)
9
8
- Submit a new issue, assuming one does not already exist.
10
9
- Clearly describe the issue including steps to reproduce when it is a bug.
11
10
- Make sure you fill in the earliest version that you know has the issue.
12
-
- Fork the repository on GitHub
13
11
14
12
## Suggesting Enhancements
15
13
16
-
I want to know what you think is missing from InfrastructureAsCode and how it can be made better.
14
+
We want to know what you think is missing from InfrastructureAsCode and how it can be made better.
17
15
18
16
- 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 it would be.
19
17
20
18
## Making Changes
21
19
22
-
-From your fork of the repository, create a topic branch where work on your change will take place.
23
-
- To quickly create a topic branch based on master; `git checkout -b my_contribution master`.
24
-
Please avoid working directly on the `master` branch.
20
+
-Create a topic branch where work on your change will take place.
21
+
- To quickly create a topic branch based on master; `git checkout -b my_contribution master`. <br>
22
+
We have policies in place to prevent direct committing on main to prevent error and malicious acts.
25
23
- Make commits of logical units.
26
24
- Check for unnecessary whitespace with `git diff --check` before committing.
27
-
- Please follow the prevailing code conventions in the repository.
28
-
Differences in style make the code harder to understand for everyone.
25
+
- Check the build workflows when creating a PR. Our standards are added in CI as much as we can.
29
26
- Make sure your commit messages are in the proper format.
30
27
31
28
```
32
29
Add more cowbell to Get-Something.ps1
33
30
34
31
The functionality of Get-Something would be greatly improved if there was a little
35
32
more 'pizzazz' added to it. I propose a cowbell. Adding more cowbell has been
36
-
shown in studies to both increase one's mojo, and cement one's status
37
-
as a rock legend.
33
+
shown in studies to both increase one's work satisfaction, and cement one's status
34
+
as a rock legend. We gotta have more cowbell!
38
35
```
39
36
40
37
- Make sure you have added all the necessary Pester tests for your changes.
41
38
- Run _all_ Pester tests in the module to assure nothing else was accidentally broken.
42
39
43
40
## Documentation
44
41
45
-
I am infallible and as such my documenation needs no corectoin.
46
-
In the highly unlikely event that that is _not_ the case, commits to update or add documentation are highly apprecaited.
42
+
There is always something to improve in documentation. Please let us know via an issue or share a PR to improve our documentation.
47
43
48
44
## Submitting Changes
49
45
50
-
- Push your changes to a topic branch in your fork of the repository.
51
-
- Submit a pull request to the main repository.
52
-
- Once the pull request has been reviewed and accepted, it will be merged with the master branch.
53
-
- Celebrate
46
+
- Push your changes to a topic branch.
47
+
- Submit a pull request to the main branch.
48
+
- Once the pull request has been reviewed and accepted, it will be merged with the main branch.
49
+
- Celebrate 🎊
54
50
55
51
## Additional Resources
56
52
@@ -59,4 +55,3 @@ In the highly unlikely event that that is _not_ the case, commits to update or a
0 commit comments