Skip to content

Make workflow safe to run locally (no git reset)#169

Merged
rmunn merged 16 commits into
masterfrom
chore/make-build-safe-for-local-git
Dec 3, 2021
Merged

Make workflow safe to run locally (no git reset)#169
rmunn merged 16 commits into
masterfrom
chore/make-build-safe-for-local-git

Conversation

@rmunn
Copy link
Copy Markdown
Collaborator

@rmunn rmunn commented Dec 3, 2021

If running the workflow locally using act or docker run, we don't want any git reset --hard HEAD commands being run on the mounted repo, as that could easily blow away uncommitted work in the developer's own copy of the repo. So we mount the repo somewhere else, and then copy the repo into a working location that we can safely run git reset inside.


This change is Reviewable

rmunn added 16 commits December 3, 2021 09:53
If running the workflow locally using `act` or `docker run`, we don't
want any `git reset --hard HEAD` commands being run on the mounted repo,
as that could easily blow away uncommitted work in the developer's own
copy of the repo. So we mount the repo somewhere else, and then copy the
repo into a working location that we can safely run `git reset` inside.

Note that this commit won't build, as the packages aren't going to be
collected properly. The package location will be changed later.
FLExBridge dependencies were getting unpacked automatically by the
Docker COPY command, but now that they're being copied from within the
build, we need to actually unpack them ourselves.
Using a sentinel file that should still exist after build
@rmunn rmunn merged commit 5675ad5 into master Dec 3, 2021
@rmunn rmunn deleted the chore/make-build-safe-for-local-git branch December 3, 2021 06:18
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.

1 participant