fix: CI-CD Optimisation #1811
fix: CI-CD Optimisation #1811
Conversation
naman9271
requested review from
AayushSaini101,
Amzani,
Shurtu-gal,
Souvikns and
asyncapi-bot-eve
as code owners
🦋 Changeset detectedLatest commit: 13d756a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Changeset has been generated for this PR as part of auto-changeset workflow.Please review the changeset before merging the PR.If you are a maintainer or the author of the PR, you can change the changeset by clicking here Tip If you don't want auto-changeset to run on this PR, you can add the label |
|
We require all PRs to follow Conventional Commits specification. |
|
|
@Amzani, @Shurtu-gal, @AayushSaini101, @Souvikns please review |
Shurtu-gal
left a comment
Shurtu-gal
left a comment
There was a problem hiding this comment.
- Could you provide a test run of the Github workflows?
- What I have generally observed is adding more complexity leads to more problems down the line? Changeset generation skipping is fine but rest optimizations are not needed imo as the amount of time it takes to verify if it needs to be done, the action will be done with its work.
Also changeset generation's need is more nuanced 🤷🏻
|
3 participants
Fixes #1806