RD-4#10
Conversation
|
I also need to test the dispatch works correctly, but is there any information that should always be present ie , python version for pypi packages, whether python_test.yml is passing etc |
|
an example of this renalreg/radar#70 |
|
Is it possible to have Public and Private versions? Assuming that some badges like actions passing can still be used on the Private ones. |
|
@George-D-S i have added the option to define public and private repos and there respective 'defaults' anything else that is needed. otherwise I think all that is left is to sign in to the services detailed on the ticket( i do not have access to this) |
|
I will review this by adding it to cool stuff and approve depending on the results. Not sure this will be till the end of the week though |
|
@andyatterton did you manage to get round to reviewing this, if not I will chase it up when I am back |
|
I did not yet have chance but will take a look next week |
andyatterton
left a comment
There was a problem hiding this comment.
Now realise that I can not add it to cool stuff without it being merged. I have had a look and it looks fine so I think merge it then I will have a play.
GitHub Repo - "Tidy" Badges
the ticket asked for the RADAR repo to be cleaned up with badges and potential of creating a reusable 'template' for this as such i have created a new workflow.
This should allow all repository READMEs to be updated using a consistent standard, while also supporting enabled and disabled badges.
Badges are only updated organization-wide when update_badges.py is modified.
Badge behavior is controlled by the presence of a badges.yml file, where badges can be enabled, disabled, or hardcoded.
