patternfly / patternfly/patternfly-react
Bug - Build - Org and React can become out of sync resulting in build failures.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 862
- Forks
- 392
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 9
Description
If an update in react requires additional updates in org were a react release is required to update org we can get stuck in a scenario where we will be unable to release Patternfly react. In order to prevent this we need the ability to build and release without the need to generate and post documentation to account for these scenarios. An update needs to be added to github actions to handle this use case.
Jira Issue: PF-41
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the repository's GitHub Actions workflows and the existing React build and release flow. Trace where documentation is generated and posted, then verify that the release path can build and release without that documentation step when Org and React updates are out of sync. Done means the workflow supports this recovery path without breaking the normal release process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, react, typescript
- Domain
- build-system, ci-cd, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100