Solutions to the Advent of Code 2024 challenges.
|,\/,| |[_' |[_]) |[_]) \\//
||\/|| |[_, ||'\, ||'\, ||
___ __ __ ____ __ __ ____ _ _ __ __
// ' |[_]| |[_]) || ((_' '||' |,\/,| //\\ ((_'
\\_, |[']| ||'\, || ,_)) || ||\/|| //``\\ ,_))
,;7,
_ ||:|,
_,---,_ )\' '|
.'_.-.,_ '. ',') j
/,' ___} \ _/ /
., ,1 .'' =\ _.''. ,`';_ |
.' \ (.'T ~, (' ) ',.' / ';',
\ .\(\O/)_. \ ( _Z-'`>--, .'', ;
\ | I _|._>;--'`,-j-' ; ', .'
__\_| _.'.-7 ) `'-' " ( ;'
.'.'_.'|.' .' \ ',_ .'\ /
| | |.' / \ \ l \ /
| _.-' / '. ('._ _ ,.' \i
,--' ---' / k _.-,.-|__L, '-' ' () ;
'._ ( '; ( _-} |
/ ' \ ; ',.__; () /
/ | ; ; ___._._____.: :-j
| \,__',-' ____: :_____.: :-\
| F : . ' ' , L
', J | ; j |
\ | | L | J
; .-F | ; J L
\___,---' J'--: j,---,___ |_ |
| |'--' L '--| '-'|
'.,L |----.__ j.__.'
| '----' |, '-' }
j / ('-----';
{ "---'--;' } |
| | '.----,.'
',.__.__.' |=, _/
| / | '.
|'= -x L___ '--,
L __\ '-----'
'.____)
In order to make contributions to this repo, you will need to authenticate git
with your GitHub account. The easiest way to do this is to use
GitHub Desktop, as it should handle this
for you.
Alternatively, create a Personal Access Token, or set up SSH.
After this is set up, you can either clone this repo using GitHub desktop,
using the command line with
git clone https://github.com/NathanielJS1541/AoC_2024.git, or if you're using
SSH do git clone [email protected]:NathanielJS1541/AoC_2024.git.
This should just prevent treading on each others toes, and loss of work etc.
- Do not commit any of the puzzle texts or inputs from Advent of Code to this repo, as AoC does not allow redistribution.
- Work in your own branch, and create a Pull Request to merge your work into main periodically. You can complete this PR yourself, but it makes it easy to identify what was added by who.
- Avoid rebasing. This has the potential to create confusing scenarios for others, or overwrite others work if they have based work on a commit that you rebase.
- Do not
git push --forceinto shared branches! People can and will lose work this way. - Create your own named folder inside the root of this repo to reflect your
name, for example
AoC_2024/bob. From there you can structure it however you like, and create your own README.md that can be linked to the contributors section below. - Use a
.gitignorefile locally within your own folder..gitignorefiles are applied to the directory they are in, and any subdirectories below that. Because there will be lots of additions to the.gitignorefile with each language people use, having them within your own folder means they can be customised to the languages you are using much easier. GitHub maintains a repo of .gitignore templates if you need some inspiration. - There is a
.gitignorein the root of the repo, which contains the.gitignoretemplates for various common IDE's (Visual Studio, VSCode, JetBrains etc.). If your IDE needs some files ignored in the.gitignore, it should be added here to ensure any dotfiles your IDE generates when you open the repo are ignored, as these are usually placed in the root.
Here you can get links to the READMEs within everyone's folder.