Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #1160
You might have to change some security settings to give write permission to the workflow. I have set it up to run when it detects any tasks were added or modified.
The current implementation checks if a
csv
file exists and if so updates it (which in turn writes the markdown table). Otherwise it loops through all the tasks and creates the DataFrame. The reason for creating the csv was because it needs to load the Task to get the number of samples and so needs a database to hold the tasks already scanned. Without these columns, I think it shouldn't take long to parse through all the task configs each time.edit: yup will need to provide write permission of some sort. I copied the workflow from the gpt-neox repo. Should the table be modified during the PR or should it be done manualy? I think you can set a workflow to run on a schedule (not sure about that but sounds like sth that should be possible).
edit2: could also use the Google Sheets API with a developer account.