Skip to content

Latest commit

 

History

History
85 lines (55 loc) · 3.94 KB

CONTRIBUTING.md

File metadata and controls

85 lines (55 loc) · 3.94 KB
Raw

Contributing to JBoss Server Migration Tool

Welcome to the JBoss Server Migration Tool project! We welcome contributions from the community. This guide will walk you through the steps for getting started on our project.

Forking the Project

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

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

The JBoss Server Migration Tool project uses JIRA to manage issues. All issues can be found here.

To create a new issue, comment on an existing issue, or assign an issue to yourself, you'll need to first create a JIRA account.

Once you have selected an issue you'd like to work on, make sure it's not already assigned to someone else. To assign an issue to yourself, simply click on "Start Progress". This will automatically assign the issue to you.

It is recommended that you use a separate branch for every issue you work on. To keep things straightforward and memorable, you can name each branch using the JIRA issue number. This way, you can have multiple PRs open for different issues. For example, if you were working on CMTOOL-338, you could use CMTOOL-338 as your branch name.

Setting up your Developer Environment

You will need:

First cd to the directory where you cloned the project (eg: cd wildfly-server-migration)

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

git remote add upstream https://github.com/wildfly/wildfly-server-migration

To build the project 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 JIRA issue you worked on in the title of your pull request and in your commit message. For example, for CMTOOL-338, the PR title and commit message should be [CMTOOL-338] adds socket binding dependencies to identify which group to update.

  3. Please include the link to the JIRA issue you worked on in the description of the pull request. For example, if your PR adds a fix for CMTOOL-338, the PR description should contain a link to https://issues.redhat.com/browse/CMTOOL-338.

For an example of a properly formatted PR, take a look at wildfly#294