All types of contributions are encouraged and valued. See the Table of contents for different ways to help and details about how this project handles them. 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. We look forward to your contributions.
And if you like the 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, which we would also be very happy about:
- Star the project
- Tweet about it
- Refer this project in your project's readme
- Mention the project at local meetups and tell your friends/colleagues
- I have a question
- I want to contribute
Before you ask a question, it is best to search for existing issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
If you then still feel the need to ask a question and need clarification, please follow the steps in Reporting bugs.
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible:
- Make sure that you are using the latest version.
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions.
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the bug tracker.
- Also make sure to search the internet to see if users outside of the GitHub community have discussed the issue.
- Collect information about the bug:
- Axis device model
- Axis device firmware version
- Stack trace
- OS and version (Windows, Linux, macOS, x86, ARM)
- Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant
- Possibly your input and the output
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
- Open an issue.
- Explain the behavior you would expect and the actual behavior.
- Please provide as much context as possible and describe the reproduction steps that someone else can follow to recreate the issue on their own.
- Provide the information you collected in the previous section.
Once it's filed:
- The project team will label the issue accordingly.
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps. Bugs without steps will not be addressed until they can be reproduced.
- If the team is able to reproduce the issue, it will be prioritized according to severity.
This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
- Make sure that you are using the latest version.
- Read the documentation carefully and find out if the functionality is already covered, maybe by an individual configuration.
- Perform a search to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
- Find out whether your idea fits with the scope and aims of the project. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset.
Enhancement suggestions are tracked as GitHub issues.
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as many details as possible.
- Describe the current behavior and explain which behavior you expected to see instead and why. At this point you can also tell which alternatives do not work for you.
- You may want to include screenshots and animated GIFs which help you demonstrate the steps or point out the part which the suggestion is related to.
- Explain why this enhancement would be useful to most users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
Start by forking the repository, i.e. copying the repository to your account to grant you write access. Continue with cloning the forked repository to your local machine.
git clone https://github.com/<your username>/AxisCommunications/docker-compose-acap.gitNavigate into the cloned directory and create a new branch:
cd docker-compose-acap
git switch -c <branch name>Update the code according to your requirements, and commit the changes using the conventional commits message style:
git commit -a -m 'Follow the conventional commit messages style to write this message'Continue with pushing the local commits to GitHub:
git push origin <branch name>Before opening a Pull Request (PR), please consider the following guidelines:
- Please make sure that the code builds perfectly fine on your local system.
- Make sure that all linters pass, see Lint of codebase
- The PR will have to meet the code standard already available in the repository.
- Explanatory comments related to code functions are required. Please write code comments for a better understanding of the code for other developers.
- Note that code changes or additions to the
.githubfolder (or sub-folders) will not be accepted.
And finally when you are satisfied with your changes, open a new PR.
A set of different linters test the codebase and these must pass in order to get a pull request approved.
When you create a pull request, a set of linters will run syntax and format checks on different file types in GitHub actions by making use of a tool called super-linter. If any of the linters gives an error, this will be shown in the action connected to the pull request.
In order to speed up development, it's possible to run linters as part of your local development environment.
Since super-linter is using a Docker image in GitHub Actions, users of other editors may run it locally to lint the codebase. For complete instructions and guidance, see super-linter page for running locally.
To run a number of linters on the codebase from command line:
docker run --rm \
-v $PWD:/tmp/lint \
-e RUN_LOCAL=true \
-e LINTER_RULES_PATH=/ \
-e VALIDATE_BASH=true \
-e VALIDATE_DOCKERFILE_HADOLINT=true \
-e VALIDATE_MARKDOWN=true \
-e VALIDATE_SHELL_SHFMT=true \
-e VALIDATE_YAML=true \
ghcr.io/super-linter/super-linter:slim-v7See .github/workflows/lint.yml for the exact setup used by this project.
It might be more convenient to run super-linter interactively. Run container and enter command line:
docker run --rm \
-v $PWD:/tmp/lint \
-w /tmp/lint \
--entrypoint /bin/bash \
-it ghcr.io/super-linter/super-linter:slim-v7Then from the container terminal, the following commands can lint the the code base for different file types:
# Lint Dockerfile files
hadolint $(find -type f -name "Dockerfile*")
# Lint Markdown files
markdownlint .
# Lint YAML files
yamllint .
# Lint shell script files
shellcheck $(shfmt -f .)
shfmt -d .To lint only a specific file, replace . or $(COMMAND) with the file path.