Hack and code

The following is the commit template for challenges/code and challenges/hack

Fill the fields in angle brackets <> as indicated in these comments. These comments will not appear in the final commit message.

• <product\> will be challenges

• <scope\> can either be code for programming or hack for ctf-hacking

• <site-name\> and <chall-code\> must conform to repository naming conventions

• <complexity\> is the blessing in codeabbey (can be a decimal), v.g. 9.33 or something else (but no parens) for hacking sites, v.g. easy or 3 or 147

• <lang\> It is the language attributed to your challenge. It is important for executing pipelines well within the repository. For more information about which characters or words are valid to place inside the commit body, see here: Configuration (opens in a new tab)

  Typically it should be equal to the progress in the score as computed by wechall.

  • Programming example chall\sol(code): #0 codeabbey, 12 (9.8)
  • Hacking example chall\sol(hack): #0 2017game-picoctf, challenge-5 (20)

Template:

<product>\sol(<scope>): #0 <site-name>, <chall-code> (<complexity>)
 
- <lang> solution, or something like this...

Full hacking example:

chall\sol(hack): #0 world-of-wargame, & d1fficult-0ne (54)

Full programming example:

chall\sol(code): #0 codeabbey, 50 (5.22)
 
- Dart solution.

Remember to make ONE commit for each challenge solution. This commit must also include the appropriate number of OTHERS solutions, which is currently 10. You must to checked the commits behind master and and commits ahead before uploading your branch. Then make ONE Merge Request with that ONE commit for ONE challenge, but ONLY after the pipeline has succeeded. See https://docs.autonomicjump.com/submission/submission-intro/ (opens in a new tab).