While it may be useful for padding my stats, it feels a bit disingenuous to
allow Github to count flake.lock updates toward my Github contributions. Am I
technically updating a file in my Github repository? Sure, but if a potential
employer were ever to take a closer look at my "contributions," I worry that it
would look bad if a good portion of them were simply the equivalent of updating
my computer. Windows users don't get "contributions" when they update, so why
should I?
Figure out a way to exclude flake.lock updates from counting towards gh
stats while preserving the ability to back up the file itself to the repo. For
example, adding flake.lock to .gitignore is not a valid solution since
flake.lock would no longer be properly updated in the Github repo.
While it may be useful for padding my stats, it feels a bit disingenuous to allow Github to count
flake.lockupdates toward my Github contributions. Am I technically updating a file in my Github repository? Sure, but if a potential employer were ever to take a closer look at my "contributions," I worry that it would look bad if a good portion of them were simply the equivalent of updating my computer. Windows users don't get "contributions" when they update, so why should I?Figure out a way to exclude
flake.lockupdates from counting towardsghstats while preserving the ability to back up the file itself to the repo. For example, addingflake.lockto.gitignoreis not a valid solution sinceflake.lockwould no longer be properly updated in the Github repo.