You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We use the action to identify changes in a specific module and trigger subsequent deployments only if need.
Now, in case of an error in the subsequent process, there is no chance to rerun the pipeline as the file change filter does not detect any files changed.
Maybe just a matter of an existing configuration we could not figure out:
How to setup the pipeline, to not filter subsequent processes wich were not successful before?
Describe alternatives you've considered?
No response
Anything else?
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@BenjaminKlatt sounds like you might want to take a look at nrwl/last-successful-commit-action other than that you’ll need to provide a more elaborate description of the problem and the solution you want with logs and pictures of the exact issue and if it can be solved by an action.
...
- name: Get branch nameid: branch-nameuses: tj-actions/branch-names@v5if: github.event_name == 'pull_request'
- uses: nrwl/last-successful-commit-action@v1id: last_successful_commitif: github.event_name == 'pull_request'with:
branch: ${{ steps.branch-name.outputs.base_ref_branch }} # Get the last successful commit on master or main branch workflow_id: 'test.yml'github_token: ${{ secrets.GITHUB_TOKEN }}
- name: Run changed-files with a custom base shaif: github.event_name == 'pull_request'id: changed-files-custom-base-shauses: tj-actions/changed-files@v20.2with:
base_sha: ${{ steps.last_successful_commit.outputs.commit_hash }}
Is this feature missing in the latest version?
Is your feature request related to a problem? Please describe.
We use the action to identify changes in a specific module and trigger subsequent deployments only if need.
Now, in case of an error in the subsequent process, there is no chance to rerun the pipeline as the file change filter does not detect any files changed.
Example
Describe the solution you'd like?
Maybe just a matter of an existing configuration we could not figure out:
How to setup the pipeline, to not filter subsequent processes wich were not successful before?
Describe alternatives you've considered?
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: