#Neurodivergent Father, Husband, Philosopher, Craftsman, and evolving Human. #FullStackDeveloper & #DevOps engineer by day and hacker by night; I'm on the lookout for my next challenge.
Location
Manassas, VA
Education
High-school in Arizona, 3043 MOS School, BS in Information Systems Security from ITT Tech
I may be missing something here, but since this comes down to creating and stashing a .json file that can be accessed in the context of a viewer on the readme.md, couldn't a repo be used just as well (with a token generated having appropriate perms to commit changes to the repo/branch that will be used in the badge to retrieve that .json file?
I may be missing something here, but since this comes down to creating and stashing a .json file that can be accessed in the context of a viewer on the readme.md, couldn't a repo be used just as well (with a token generated having appropriate perms to commit changes to the repo/branch that will be used in the badge to retrieve that .json file?
That's another way, abusing Gist just has fewer steps. And lower risk (can't accidentally give permissions to the wrong repo, just to your gists).