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
The idea of openbases is that we have components (an experiment, a testing robot, a documentation template) that are put together into larger templates. We've started to describe those here:
It would be cool and fun to be able to have simple labels (badges) that can thus describe an entire builder, to put in the top of the repo. To better support this we should also add some simple definitions for templates and components first.
The text was updated successfully, but these errors were encountered:
Oh I'm super excited about this! Of course shields.io can create custom badges in advance, eg:
Or we can have our own endpoint to (dynamically) return responses with our (updated) library of bases! This is super cool, and will be easy to do I think. First we should narrow down the list of templates / components, as I've linked above is a start.
The idea of openbases is that we have components (an experiment, a testing robot, a documentation template) that are put together into larger templates. We've started to describe those here:
https://openbases.github.io/bases/#components
Thus a complete template, what I'm calling a builder, might be something like:
It would be cool and fun to be able to have simple labels (badges) that can thus describe an entire builder, to put in the top of the repo. To better support this we should also add some simple definitions for templates and components first.
The text was updated successfully, but these errors were encountered: