Added Bugs to Keep my job

Fix tpyo

"Improve performance by removing a function that never did anything" the story of my life

"If you are reading this, you are in the wrong branch."

"idk what happened but it works fine now"

“i cant believe this works i think”

"Updated README"

"Forgot to commit changes lol"

I also apparently forgot append was a thing

"fixed"

I'm ashamed... It's simply "bump deps"

Did I also touch some code and tests connected to dependency updates. Yes.

Did I document any of that? No.

Did I spend more time writing this comment the thinking about the commit. Most definitely.

Will I be bisecting to this commit after our next deploy and cursing at myself? Probably.

this is terrible, will rewrite later

"Added missing lifecycle blocks"

" "

"push files"

(It's a personal repo for homework assignments)

• fixes #22

wip

see #234

How am I supposed to do that I'm waiting for docker to rebuild my image to know if my new configuration fucks everything

"Move from GitHub to Forgejo"

Changes

"can still be better but priority changed"

merge staging

"relearning c++ arrays again"

"fixed. whoops..."

"fix previous commit"

Notes

"formatting and typo"

...

"TLDR..."

I'm kidding, my applications are so simple version control would be synonymous with entire rewrites as I lean new things.

"Docker Compose v2"

basically had to alter a few of my Ansible recipes

(translated from German) I can't write

"Default rating"

PAPYRUSSSSSS!!!!

e12fa3b (HEAD -> main, origin/main) No

Fixes issues in PR

"src/utils/typing: added tests for isArray"

we have 90% coverage minimum

"Added brew to list of accepted package managers"

From my "install all the things" script I host on github

“Expanded unit test to cover new functionality” true story

scoping

Refactor package structure

chore: update image tag

"feat: replace every function in FunctionIdentifier with a single closure

My goal with less-function-id was to create a more neat solution but instead it turned into something far more ugly and limiting" You sometimes think a solutioniis good and neat until you implement it