Skip to content

Latest commit

 

History

History
80 lines (54 loc) · 3.65 KB

CONTRIBUTING.md

File metadata and controls

80 lines (54 loc) · 3.65 KB

Contributing guide

First off all, thank you for taking the time to contribute into WildFly AI Feature Pack! The below contents will help you through the steps for getting started with WildFly AI Feature Pack. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions.

If you like our project, but just don’t have time to contribute, that’s fine. There are other easy ways to support the project and show your appreciation.

  • Mention the project at local meetups and tell your friends/colleagues.
  • Tweet about it and also check out our twitter page and mastodon page.
  • Check out our youtube contents.

Forking the Project

To contribute, you will first need to fork the wildfly-ai-feature-pack 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-ai-feature-pack.

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!

Issues

WildFly AI Feature Pack uses GitHub Issues to manage issues. All issues can be found here.

Setting up your Developer Environment

You will need:

First cd to the directory where you cloned the project (eg: cd wildfly-datasources-galleon-pack)

Add a remote ref to upstream, for pulling future updates. For example:

git remote add upstream https://github.com/wildfly-extras/wildfly-ai-feature-pack

To build wildfly-ai-feature-pack run:

mvn clean install

To skip the tests, use:

mvn clean install -DskipTests=true

To run only a specific test, use:

mvn clean install -Dtest=TestClassName

Contributing Guidelines

When submitting a PR, please keep the following guidelines in mind:

  1. 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!

  2. Please include the GitHub issue you worked on in the title of your pull request and in your commit message.

  3. Please include the link to the GitHub issue you worked on in the description of the pull request.

Lastly, this project is an open source project. Please act responsibly, be nice, polite and enjoy!