Welcome to the WildFly cekit modules project! We welcome contributions from the community. This guide will walk you through the steps for getting started on our project.
All contributions to this repository are licensed under the Apache License, version 2.0 or later, or, if another license is specified as governing the file or directory being modified, such other license.
All contributions are subject to the Developer Certificate of Origin (DCO). The DCO text is also included verbatim in the dco.txt file in the root directory of the repository.
All contributions must comply with applicable laws and regulations, including U.S. export control and sanctions restrictions. For background, see the Linux Foundation’s guidance: Navigating Global Regulations and Open Source: US OFAC Sanctions.
To contribute, you will first need to fork the wildfly-cekit-modules repository.
This can be done by looking in the top-right corner of the repository page and clicking "Fork".
The next step is to clone your newly forked repository onto your local workspace.
This can be done by going to your newly forked repository, which should be at https://github.com/USERNAME/wildfly-cekit-modules.
Then, there will be a green button that says "Code". Click on that and copy the URL.
Then, in your terminal, paste the following command:
git clone [URL]Be sure to replace [URL] with the URL that you copied.
Now you have the repository on your computer!
This project uses Github Issues to manage issues. All issues can be found here.
You will need:
- Git
- bats
- An IDE (e.g., IntelliJ IDEA, Eclipse, etc.)
First cd to the directory where you cloned the project (eg: cd wildfly-cekit-modules)
Add a remote ref to upstream, for pulling future updates. For example:
git remote add upstream https://github.com/wildfly/wildfly-cekit-modules
When updating or adding a new cekit module, make sure to add and run bats tests.
Tests are located inside the cekit module in the test directory.
To run bats tests (example using the elytron cekit module):
bats jboss/container/wildfly/launch/elytron/test/elytron.bats
To run all tests:
sh ./run
When submitting a PR, please keep the following guidelines in mind:
-
In general, it's good practice to squash all of your commits into a single commit. For larger changes, it's ok to have multiple meaningful commits. If you need help with squashing your commits, feel free to ask us how to do this on your pull request. We're more than happy to help!
-
Please include the GitHub issue you worked on in the title of your pull request and in your commit message.
-
Please include the link to the GitHub issue you worked on in the description of the pull request.