mirror of
https://github.com/docker/build-push-action.git
synced 2024-11-23 17:26:10 +08:00
65e18bfb3c
CONTRIBUTING and SUPPORT guidelines Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
32 lines
1.6 KiB
Markdown
32 lines
1.6 KiB
Markdown
# Support [](https://isitmaintained.com/project/docker/build-push-action)
|
|
|
|
First, [be a good guy](https://github.com/kossnocorp/etiquette/blob/master/README.md).
|
|
|
|
## Reporting an issue
|
|
|
|
Please do a search in [open issues](https://github.com/docker/build-push-action/issues?utf8=%E2%9C%93&q=) to see if the issue or feature request has already been filed.
|
|
|
|
If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment.
|
|
|
|
:+1: - upvote
|
|
|
|
:-1: - downvote
|
|
|
|
If you cannot find an existing issue that describes your bug or feature, submit an issue using the guidelines below.
|
|
|
|
## Writing good bug reports and feature requests
|
|
|
|
File a single issue per problem and feature request.
|
|
|
|
* Do not enumerate multiple bugs or feature requests in the same issue.
|
|
* Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
|
|
|
|
The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix.
|
|
|
|
You are now ready to [create a new issue](https://github.com/docker/build-push-action/issues/new/choose)!
|
|
|
|
## Closure policy
|
|
|
|
* Issues that don't have the information requested above (when applicable) will be closed immediately and the poster directed to the support guidelines.
|
|
* Issues that go a week without a response from original poster are subject to closure at our discretion.
|