Skip to content
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

Open
ndeet opened this issue Feb 21, 2022 · 5 comments
Open

Github workflow/action based files in SVN #84

ndeet opened this issue Feb 21, 2022 · 5 comments
Labels
help wanted Extra attention is needed type:bug Something isn't working.

Comments

@ndeet
Copy link

ndeet commented Feb 21, 2022

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

  1. Create a tag so the deployment workflow
  2. Check the deployed files on WordPress SVN repo

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?

@vikrampm1 vikrampm1 added the type:bug Something isn't working. label Feb 22, 2022
@vikrampm1 vikrampm1 moved this to Incoming in Open Source Practice Feb 22, 2022
@jeffpaul
Copy link
Member

@ndeet can you please link to your repo / latest action run to better triage?

@jeffpaul jeffpaul self-assigned this Feb 22, 2022
@jeffpaul jeffpaul added the needs:feedback This requires reporter feedback to better understand the request. label Feb 22, 2022
@jeffpaul jeffpaul moved this from Incoming to In Progress in Open Source Practice Feb 22, 2022
@ndeet
Copy link
Author

ndeet commented Feb 22, 2022

@jeffpaul
Copy link
Member

@ndeet I'm not seeing an immediate cause here, but adding those files to your .distignore should remove them from SVN and stop from having them sent in the future. I'll keep this open in case others can jump in and help triage why those files are introduced and if there's a way to protect for that within the action itself.

@jeffpaul jeffpaul added the help wanted Extra attention is needed label Feb 23, 2022
@jeffpaul jeffpaul removed their assignment Feb 23, 2022
@richard-muvirimi
Copy link
Contributor

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

@github-actions
Copy link

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.

Repository owner moved this from In Progress to Merged in Open Source Practice Jun 29, 2022
@dinhtungdu dinhtungdu removed the needs:feedback This requires reporter feedback to better understand the request. label Aug 15, 2022
@dinhtungdu dinhtungdu reopened this Aug 15, 2022
Repository owner moved this from Merged to In Progress in Open Source Practice Aug 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed type:bug Something isn't working.
Projects
Status: In Progress
Development

No branches or pull requests

5 participants