That's a great idea! that way, the user don't need to include the comment tag name for the action to search for where they want to put the badge, users just have to point the image url to where the generated JSON file will be.
I did consider that approach initially, however decided not to do it because of 2 user experience reasons.
I didn't really want to create additional files in the user's repository, so i rather the workflow update the README rather than generating a new JSON file and updating it.
I would also expect that if anyone uses them, a lot will people who already uses blog-post-workflow, so I wanted to keep the inputs consistent with that workflow.
I also find the Shields endpoint a little too complicated to understand, that's why in this action I'm just creating CDN links rather than generating endpoints.
I did check out your project though, really liked that you have a Dockerfile and also tests. 😄
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That's a great idea! that way, the user don't need to include the comment tag name for the action to search for where they want to put the badge, users just have to point the image url to where the generated JSON file will be.
I did consider that approach initially, however decided not to do it because of 2 user experience reasons.
I also find the Shields endpoint a little too complicated to understand, that's why in this action I'm just creating CDN links rather than generating endpoints.
I did check out your project though, really liked that you have a Dockerfile and also tests. 😄