Adrian Cowan

For my 2 cents, I think having a popup of some kind is clearer than just changing the button text as that might get missed. On the other hand, I...

(re: end goal) Might also be worth considering number of users that skip the task as well as mark it unanswerable.

UI-wise how about something like this (I'm wary of too many buttons and clutter on mobile), the wording is just an example. 

I'll take this on, it'll give me a change to learn some of the backend code.

During the front end teams call there was some discussion about `ack`-ing and `nack`-ing and it thought that maybe the `nack` could include a reason for rejecting/skipping the task. In...

I had to disable the `ack`ing temporarily as the backend currently rejects a `nack` after an `ack`, but this is what it looks like so far (the backend is receiving...

There are some fundamental questions about the how skipping should work in the discord website channel that we need to resolve. The code is at a proof-of-concept stage, it needs...

Additional examples: * Not triggering if no web or backend change https://github.com/othrayte/Open-Assistant/pull/3 * Triggering on backend change https://github.com/othrayte/Open-Assistant/pull/4

@yk, that's something I didn't consider, though if I'm reading https://github.com/docker/metadata-action#latest-tag correctly the latest tag should not be updated on the push and pr builds, just the release (tag) one....

I've just raised an alternative simpler PR as an option that should have less potential for fallout. Take a look. #439