biocompute-objects / biocompute-objects/BCO_Documentation

Example of a BCO as a GitHub action

Open
#82 0 comments 0 reactions 0 assignees View on GitHub
discuss enhancement
Dominant language
HTML
Stars
17
Forks
13
PR merge metrics
No merged PRs in 30d

Description

From: [De Almeida, Jonas (NIH/NCI) [E]](@jonasalmeida)

Hi Charles,

As promised Thursday, the note on running workflows in github:

`40M developers on github woke up last week with a new tab, “actions”, and a workflow engine integrated in their developer environment – which already includes hosting web applications and authentication services, all of this with versioning and a marketplace where workflows can be published and found. So the conversation Thursday was about creating a BCO example in this environment to establish its FAIR use. I suspect most developers (definitely most students) have already migrated to serverless execution environments and having a one-click place where to validate, and disseminate, a workflow manifest/language, really is the place to be if you want to reach them. So the suggestion is to have a simple and compelling example of a BCO as a github action others can fork and investigate.`

References:

1. [Github documentation](https://help.github.com/en/actions/automating-your-workflow-with-github-actions)
2. Keynote at github universe explaining workflow actions: Here’s a link to a [video](https://youtu.be/9EoNqyxtSRM?t=693)
I left the same comment in gitter [this one :smile:] in case you want to discuss it further (not a fan of email conversations here …)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked GitHub Actions documentation and review the BCO_Documentation repository to determine where an example belongs. The issue does not name a file, test, or concrete validation steps; done would be a simple, compelling BCO example that others can fork and investigate.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
devops, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.