fix: append working_directory to filename
#63
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
owenrumney
approved these changes
Jun 1, 2022
|
thanks @smaeda-ks |
Open
3ware-release bot
pushed a commit
to 3ware/workflows
that referenced
this pull request
Feb 2, 2023
## [1.0.2](v1.0.1...v1.0.2) (2023-02-02) ### Chores * **deps:** bump amannn/action-semantic-pull-request from 4 to 5 ([#7](#7)) ([3958e45](3958e45)), closes [#205](https://github.com/3ware/workflows/issues/205) [#205](https://github.com/3ware/workflows/issues/205) [#194](https://github.com/3ware/workflows/issues/194) [#179](https://github.com/3ware/workflows/issues/179) [#177](https://github.com/3ware/workflows/issues/177) [#174](https://github.com/3ware/workflows/issues/174) [#207](https://github.com/3ware/workflows/issues/207) [#205](https://github.com/3ware/workflows/issues/205) [#205](https://github.com/3ware/workflows/issues/205) [#194](https://github.com/3ware/workflows/issues/194) [#179](https://github.com/3ware/workflows/issues/179) [#177](https://github.com/3ware/workflows/issues/177) [#174](https://github.com/3ware/workflows/issues/174) [#208](https://github.com/3ware/workflows/issues/208) [#209](https://github.com/3ware/workflows/issues/209) [#207](https://github.com/3ware/workflows/issues/207) [#206](https://github.com/3ware/workflows/issues/206) * **deps:** bump aquasecurity/tfsec-pr-commenter-action from 1.2.0 to 1.3.1 ([#9](#9)) ([4f17bf3](4f17bf3)), closes [#85](#85) [aquasecurity/tfsec-pr-commenter-action#86](aquasecurity/tfsec-pr-commenter-action#86) [aquasecurity/tfsec-pr-commenter-action#86](aquasecurity/tfsec-pr-commenter-action#86) [aquasecurity/tfsec-pr-commenter-action#65](aquasecurity/tfsec-pr-commenter-action#65) [aquasecurity/tfsec-pr-commenter-action#64](aquasecurity/tfsec-pr-commenter-action#64) [aquasecurity/tfsec-pr-commenter-action#59](aquasecurity/tfsec-pr-commenter-action#59) [aquasecurity/tfsec-pr-commenter-action#63](aquasecurity/tfsec-pr-commenter-action#63) [aquasecurity/tfsec-pr-commenter-action#78](aquasecurity/tfsec-pr-commenter-action#78) [aquasecurity/tfsec-pr-commenter-action#76](aquasecurity/tfsec-pr-commenter-action#76) [aquasecurity/tfsec-pr-commenter-action#74](aquasecurity/tfsec-pr-commenter-action#74) [aquasecurity/tfsec-pr-commenter-action#82](aquasecurity/tfsec-pr-commenter-action#82) [aquasecurity/tfsec-pr-commenter-action#65](aquasecurity/tfsec-pr-commenter-action#65) [aquasecurity/tfsec-pr-commenter-action#59](aquasecurity/tfsec-pr-commenter-action#59) [aquasecurity/tfsec-pr-commenter-action#63](aquasecurity/tfsec-pr-commenter-action#63) [aquasecurity/tfsec-pr-commenter-action#78](aquasecurity/tfsec-pr-commenter-action#78) [aquasecurity/tfsec-pr-commenter-action#76](aquasecurity/tfsec-pr-commenter-action#76) [aquasecurity/tfsec-pr-commenter-action#74](aquasecurity/tfsec-pr-commenter-action#74) [#86](#86) [#82](#82) [#74](#74) [#76](#76) [#78](#78)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a naive solution to #54 (comment)
Currently, it appears that if the
working_directoryoption is provided when using this action, it fails to lookup files due to path mismatch, which always results in the.... not writing as not part of the current PRmessage.