![]() ![]() Notehub JSīefore we get to the actual GitHub Actions workflow, let me give you just a little background on the Notehub JS project because it's a bit different than most. Today, I'll walk through how to use a GitHub Actions workflow to create (or update) a pull request whenever a new feature branch is made in that repository. The best solution I could think of was to open a new pull request in the Notehub JS repo after copying the updated openapi.yaml file into a feature branch and tagging myself to review it. Since I didn't know how often the Notehub's openapi.yaml file would be updated, I needed a way to notify myself when a new version of the Notehub's API file needed review in the Notehub JS repository. And publish the updated Notehub JS library to npm.Īnd I wanted to automate as many of these steps as possible through the use of GitHub Actions workflows.Generate a fresh version of the Notehub JS API library based on the that file via the OpenAPI Generator CLI.Open a new pull request against the Notehub JS repo with the copy of the openapi.yaml file.Make a copy of the openapi.yaml file from the Blues cloud's repository, Notehub, whenever the file was updated.It was a great learning experience for me and a new, unique challenge because I needed to do the following things: This blog post is the second in a short series I'm writing about the many things I learned in the course of building my first open source API library for the IoT startup I work for, Blues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |