feat(ctf): store solves walkthrough

[k4rt0fl3r]

Feature build upon the !ctf archive functionality.
When issuing the command !ctf archive, all pins from challenges will be uploaded to the GitHub repository defined through the config values.

More specifically, all pinned text messages will be written, in chronological order (oldest to newest), in a Markdown file and in case a pinned message contains has any files attached (or is just a file), the exact file will be uploaded separately and a reference to it will be added in the Markdown file. All files will be stored in the repo following this file structure: {ctf-name}/{challenge-name}/

[apogiatzis]

@eioake01 Thanks for your valuable contributions!! Just a minor suggestion, can you please rename methods/vars to snake case such that they conform to PEP-8?

Finally, make sure that you run the code through the black formatter before pushing to keep a consistent style within the codebase.

[k4rt0fl3r]

@eioake01 Thanks for your valuable contributions!! Just a minor suggestion, can you please rename methods/vars to snake case such that they conform to PEP-8?

Finally, make sure that you run the code through the black formatter before pushing to keep a consistent style within the codebase.

Hello @apogiatzis , regarding black formatter, I just used the default formatting style, with the command black .
Is there something more specific I should do?

[k4rt0fl3r]

With the latest commit (468cee5), I made some changes as for the GitHub Requests when uploading the files to not stall. To do that, I used the asyncio lib and specifically the ensure_future functionality.

There is a slight improvment between using asyncio and not, which I believe will be more noticable with big CTFs and lots of pins.

For 2 test cases, 15 requests each (5 markdown (270 bytes each), 5 images (107KB each), 5 py files (12 bytes each ))
Without asyncio: 47s and 44s
With asyncio: 39s and 41s