Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically take nearest next CTF in edge cases #1

Open
lucidBrot opened this issue Jul 14, 2022 · 0 comments
Open

Automatically take nearest next CTF in edge cases #1

lucidBrot opened this issue Jul 14, 2022 · 0 comments
Assignees
Labels

Comments

@lucidBrot
Copy link
Member

Currently the bot chooses the active CTF based on these steps:

  1. If a ctf id was manually specified in the command, use that one.
  2. Else if a ctf id is specified in the pinned message of the channel the command was executed in, use that one.
  3. Else if a ctf is currently ongoing, use that one
  4. Else skip the ctfnote part in channel creation and complain.

In cases where the infrateam is collaborating in advance of the CTF start, or when the ctf time is set wrong, this could be made more convenient by adding a step 3.1 : If no ctf is currently ongoing but there is a unique next CTF that is not further away than N days (or weeks), use that one.

The value of N is TBD. Probably smth like 2 weeks should be fine.

Reason for not going further in time than that limit is that in those cases someone probably simply forgot to import the ctf that was meant. Better use no ctf than a wrong one. Then the user can use the fixup command.

Not urgent.

@lucidBrot lucidBrot added enhancement New feature or request ctfnote-integration labels Jul 14, 2022
@lucidBrot lucidBrot self-assigned this Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant