Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
puppet-sympa
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Adullact
puppet-sympa
Commits
5c61697a
Commit
5c61697a
authored
1 week ago
by
Fabien Combernous
Browse files
Options
Downloads
Plain Diff
Merge branch '13-add-licence-file' into 'main'
Resolve "Add Licence file" Closes
#13
See merge request
!12
parents
30401b58
c681fd2e
No related branches found
No related tags found
1 merge request
!12
Resolve "Add Licence file"
Pipeline
#93641
canceled
1 week ago
Stage: syntax
Stage: unit
Stage: acceptance
Changes
2
Pipelines
2
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
CONTRIBUTING.md
+27
-0
27 additions, 0 deletions
CONTRIBUTING.md
LICENSE
+661
-0
661 additions, 0 deletions
LICENSE
with
688 additions
and
0 deletions
CONTRIBUTING.md
0 → 100644
+
27
−
0
View file @
5c61697a
If you follow these contributing guidelines your patch
will likely be included into a release a little more quickly.
## Contributing
1.
Fork the repo.
2.
Create a separate branch for your change.
3.
We only take merge requests with passing tests, and documentation. You can also execute them locally.
4.
Checkout
[
Voxpupuli review docs
](
https://voxpupuli.org/docs/reviewing_pr/
)
. We try to
use it to review a merge request and the
[
official styleguide
](
https://www.puppet.com/docs/puppet/7/style_guide.html
)
.
They provide some guidance for new code that might help you before you submit a merge request.
5.
Add a test for your change. Only refactoring and documentation
changes require no new tests. If you are adding functionality
or fixing a bug, please add a test.
6.
Squash your commits down into logical components. Make sure to rebase
against our current master.
7.
Push the branch to your fork and submit a merge request.
Please be prepared to repeat some of these steps as your code is reviewed.
A final word: thank you very much for contributing!
This diff is collapsed.
Click to expand it.
LICENSE
0 → 100644
+
661
−
0
View file @
5c61697a
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment