urcomputeringpal/label-mutex

A GitHub Action that facilitates obtaining, releasing, and representing a lock on a shared resource using PR labels.

label-mutex's Issues

expose lock value during a failed claim

lock retention is chatty

2020/10/30 15:23:59 Lock 'deploy:staging' should already be owned by https://github.com/REDACTED/REDACTED/pull/780, confirming  ...
2020/10/30 15:23:59 Attempting to lock deploy:staging with value of https://github.com/REDACTED/REDACTED/pull/780 ...
2020/10/30 15:23:59 Error obtaining lock, tryna figure out what the current value is. 1 error occurred:
	* key already exists in table


2020/10/30 15:23:59 Lock confirmed: false, &{Partition:label Key:deploy:staging Version:1 Expires:0 value:0xc0002c6460}, 1 error occurred:
	* key already exists in table

2020/10/30 15:23:59 Weird, the lock should have already been ours!

Fix output mechanism

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see:

ref lock

optimisitic ref lock, for "auto merge" on a branch in the absence of any PR locks

report success if attempt to remove a lock fails due to a mismatch

Don't fail when closing a PR that didn't ever want a lock

2020/11/03 16:50:17 Unlocking 'deploy:staging' ...
2020/11/03 16:50:17 Attempting to unlock deploy:staging with value of https://github.com/REDACTED/REDACTED/pull/815 ...
2020/11/03 16:50:18 Unlocked!
Error: error while processing event: 1 error occurred:
	* key not found in table

move docker image to ghcr.io

Release v0.4.0

• GCS support

GCS support

see https://github.com/mco-gh/gcslock

Tasks

Beta Give feedback

1. https://github.com/fsouza/fake-gcs-server
2. lock library
3. integration
4. configuration
5. https://github.com/urcomputeringpal/label-mutex-test/pull/1
6. GCS docs #19
   docker:pr-image +1
7. polish, announcement, release