event assignment default

[Keyrxng]

Resolves #19

• fallback to assignment event timestamp if the bot has not intervened since the contributor started the task via any method.
• updated tests

[github-actions]

Unused types (1)

Filename	types
src/types/github-types.ts	Label

[0x4007]

Where's QA link? Code looks fine.

[Keyrxng]

Where's QA link? Code looks fine.

My bad

QA:

https://github.com/ubq-testing/user-activity-watcher/actions/runs/10834775241/job/30064760402
ubq-testing/sandbox#2

[0x4007]

Is there a simple way you can prove that this works in some mock example with shorter timeouts? Like link a GitHub issue

[Keyrxng]

Is there a simple way you can prove that this works in some mock example with shorter timeouts? Like link a GitHub issue

ubq-testing/command-start-stop#19 < this was created on the 4th, so last week. My config settings are the default 3.5 and 7 days respectively.

The issue is filled with usage of /start but no official start comment from the bot. Is this enough or you mean run a very specific couple of tests?

[gentlementlegen]

I think what we are trying to solve is users that self assign through the UI. There is no start message from the bot (there is, but it is different). In this scenario I noticed that the reminders and unassigns were not working.
Example: https://github.com/ubiquibot/user-activity-watcher/actions/runs/10835091739/job/30065821594#step:5:53

[Keyrxng]

here is a clear cut example from that same run.

self assigned via the UI, bot kicked me.

[Keyrxng]

Here is a run I just done with a 5m warning and 10m disqualification

https://github.com/ubq-testing/user-activity-watcher/actions/runs/10835251567/job/30066345978

[gentlementlegen]

The code seems to be indented with 4 spaces instead of the usual 2 spaces.

[0x4007]

Fix CI and lets merge.

[Keyrxng]

fixing ci rn, new log means update tests. Tedious but essential

The code seems to be indented with 4 spaces instead of the usual 2 spaces.

Yeah idk why that happens in certain repos, I always have format-on-save enabled and it works right most of the time. It's not like there is a config file in this repo that's affecting it either, weird af.