-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github workflow/action based files in SVN #84
Comments
@ndeet can you please link to your repo / latest action run to better triage? |
Hi @jeffpaul thanks for the quick reply. The GH action run: The SVN Repo: Thank you. |
@ndeet I'm not seeing an immediate cause here, but adding those files to your |
These files are created by the docker image used for composer setup, you can refer to the issue that explains the use of a docker image Automatically created docker packages after using this action |
This issue has been automatically closed because there has been no response to our request for more information. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. See this blog post on bug reports and the importance of repro steps for more information about the kind of information that may be helpful. |
Describe the bug
The Github workflow run produces three new files that end up in the SVN. Not sure if they are new or have been there for some time and this is known but I get these unrelated files in the SVN:
DOCKER_ENV
docker_tag
output.log
Not sure if it matters but I use a composer based deployment step that runs
composer install
that could cause this?Steps to Reproduce
Expected behavior
Not sure but those files seems to contain debugging information not relevant to the published plugin.
Is it save to add those three files to
.distignore
?The text was updated successfully, but these errors were encountered: