The action can be found in devops-actions/load-used-actions. Loading the information is done by another action that loads all repositories’ workflow files and outputs a list of all the actions in use in them, with the information of which workflow uses with action and version of it. This way my users can see examples of their usages and I can easily find the implementations in case there is something wrong with the action, like a security vulnerability or newer features being implemented. Next to prettifying the marketplace and adding search, I want to add more information about the actions being used inside of our production environment. The goal is to give our users a place where they can find the supported actions internally, since we block the use of public actions in our production organization. You can read more information about the Internal GitHub Actions Marketplace I created in this blog post. Open Source FTW!Īctions have to be Open Source to be able to use them by default (you can use private repos, but that is a bit more work), So if you miss something, you can start a conversation with the maintainer (use issues or discussions if they have that enabled) and even send in a Pull Request to propose the fix! The upload-action was missing some features that I needed for this project. This is the important step for later usage of the data: store it inside the repository that holds the Internal GitHub Marketplace.įor this I use this GitHub Action where I have added the option to upload the files into a branch: Since the GitHub Pages website from this repo runs on a gh-pages branch, I needed to upload the file in the same branch. It doesnt behave the way I thought it would. Upload the json to the GitHub Actions Marketplace 1 Im trying to streamline and automate publishing of my Actions to the GitHub Actions Marketplace.
Github actions marketplace download#
To view the results in the workflow run, I upload the json file as an artefact so I can download and check it if needed. Upload the json as an artefact for easy testing We store the output of the load-available-actions action in a file so we can upload it more easily to both the artefacts for this run (handy for testing and validation) and to the GitHub Actions Marketplace repo. Store the outcome of the previous step as json It loops through all the repos, scans for either an action.yml or actions.yaml in the root of the repository and adds the information to the output of this step so that it can be used later on in the workflow. It needs a token to access the GitHub API and will load all repositories it can find from either the user or the organization you give it. I created the load-available-actions action just for this purpose. Load available actions from an organization
Jobs : get-action-data : runs-on : ubuntu-latest steps : - uses : name : Load available actions id : load-actions with : PAT : $ repo : actions-marketplace branch-name : gh-pages Workflow stepsīelow I listed the steps in the workflow that do the actual work.
0 kommentar(er)
