From d3f5940fce1d6647486305ed24c6b0e3ec3a7423 Mon Sep 17 00:00:00 2001 From: Kashish Mittal <113269381+04kash@users.noreply.github.com> Date: Tue, 7 Jan 2025 03:34:01 +0400 Subject: [PATCH] add instuctions on how to use the version bump workflow (#243) Signed-off-by: Kashish Mittal --- CONTRIBUTING.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 480a3867f..c69e28c69 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,7 +19,10 @@ The `redhat-developer/rhdh-plugins` repository is designed as a collaborative sp - [Migrating a plugin](#migrating-a-plugin) - [Manual migration steps](#manual-migration-steps) - [Using the cli to migrate plugins from janus-idp/backstage-plugins](#using-the-cli-to-migrate-plugins-from-janus-idpbackstage-plugins) + - [Next steps](#next-steps) + - [Maintenance of older versions](#maintenance-of-older-versions) - [API Reports](#api-reports) + - [Keeping Workspaces Upto Date with Backstage](#keeping-workspaces-upto-date-with-backstage) - [Submitting a Pull Request](#submitting-a-pull-request) ## License @@ -251,6 +254,10 @@ There are two ways you can do this: Each plugin/package has its own API Report which means you might see more than one file updated or created depending on your changes. These changes will then need to be committed as well. +## Keeping Workspaces Upto Date with Backstage + +To keep plugins in the various workspaces up to date with Backstage we have a [Version Bump Workflow](https://github.com/redhat-developer/rhdh-plugins/actions/workflows/version-bump.yml) in place, similar to the one that is used in the [backstage/community-plugins](https://github.com/backstage/community-plugins) repository. For instructions on how to use this workflow, refer to the guidelines in this document: https://github.com/backstage/community-plugins/blob/main/docs/version-bump.md#process. + ## Submitting a Pull Request When you've got your contribution working, tested, and committed to your branch it's time to create a Pull Request (PR). If you are unsure how to do this GitHub's [Creating a pull request from a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) documentation will help you with that.