Skip to content

Conversation

@RyanCarrier
Copy link

Just a simple one to make my small runs on self hosted runners go faster.
CACHE_PATH includes the version so we only need to check that. The only concern would be if they set their own cache path

@bartekpacia
Copy link
Collaborator

Hi, thanks for the PR.

If I understand correctly, this adds a new check-cache input. Please update the action YAML file and the README accordingly.

@RyanCarrier
Copy link
Author

Nope the check-cache is the id of the workflow step, so the next step we can choose to not redownload flutter if it'a already there. No user facing changes

Comment on lines +116 to +121
if [ -d "${{ steps.flutter-action.outputs.CACHE-PATH }}" ]; then
echo "Cache path already exists, skipping cache step."
echo "flutter-action-cache-exists=true" >> "$GITHUB_OUTPUT"
else
echo "flutter-action-cache-exists=false" >> "$GITHUB_OUTPUT"
fi
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of setting an env var, let's add a new value to outputs of this action (starting at line 54 in this file).

Then please also update the README so that others can learn about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants