backstage / backstage/community-plugins
🚀 amplication: Action Examples
- Dominant language
- TypeScript
- Stars
- 422
- Forks
- 697
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 286
Description
### Workspace
amplication
### 🔖 Feature description
It would be great to have examples added to this plugin so that way they show up in the [installed actions](https://demo.backstage.io/create/actions) making it easier for people to self service this actions.
### 🎤 Context
It would be great to have examples added to this plugin so that way they show up in the [installed actions](https://demo.backstage.io/create/actions) making it easier for people to self service this actions.
### ✌️ Possible Implementation
Add examples using the examples feature, examples of how to do this can be found here: https://github.com/backstage/community-plugins/blob/302611256ef16b3fbcaace16767f44931231cc30/workspaces/azure-devops/plugins/scaffolder-backend-module-azure-devops/src/actions/devopsRunPipeline.examples.ts#L20-L37 and here: https://github.com/backstage/community-plugins/blob/302611256ef16b3fbcaace16767f44931231cc30/workspaces/azure-devops/plugins/scaffolder-backend-module-azure-devops/src/actions/devopsRunPipeline.ts#L59
### 👀 Have you spent some time to check if this feature request has been raised before?
- [x] I checked and didn't find similar issue
### 🏢 Have you read the Code of Conduct?
- [x] I have read the [Code of Conduct](https://github.com/backstage/community-plugins/blob/main/CODE_OF_CONDUCT.md)
### Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else
Contributor guide
Research direction
Start by reviewing the linked devopsRunPipeline.examples.ts and devopsRunPipeline.ts files to understand the examples feature, then locate the corresponding amplication action files in this repository. Add examples following that pattern and verify that they appear for the installed actions in the linked Backstage actions page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100