You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very useful if all GT repos which (successfully) used this template could be easily identified as such on Github.
The best way to achieve this IMO would be to have the gtrepo workflow add a step which uses the Github API (and Github Action Token) to add the topic automatically.
For the concrete string I would propose ocr-d-gt.
The next best thing at the moment is a Github search for the strings in the generated Readme.
The text was updated successfully, but these errors were encountered:
BTW, the above Github search does not even cover GT repos like the ones from ULB Halle, probably because their readme has been edited or is from an earlier version of the template.
I could not find any documentation on an official way to track instances of a template. There are repeated feature requests for this, and some discussions on workarounds, esp. on how to synchronise the instances with changes from upstream. For the latter, there is even a Github Action. Maybe we should include this ASAP so at least from then on new repos will easily be synced.
BTW, the above Github search does not even cover GT repos like the ones from ULB Halle, probably because their readme has been edited or is from an earlier version of the template.
It would be very useful if all GT repos which (successfully) used this template could be easily identified as such on Github.
The best way to achieve this IMO would be to have the gtrepo workflow add a step which uses the Github API (and Github Action Token) to add the topic automatically.
For the concrete string I would propose
ocr-d-gt
.The next best thing at the moment is a Github search for the strings in the generated Readme.
The text was updated successfully, but these errors were encountered: