You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given an mono-repo marketplace, comprised of many packages that have their own release numbers, what would be considered a best practice for expressing a github release within that github repo? Is it even necessary?
I'm looking at it as a sort of quick check that people can do when visiting the repo, but I suppose they can hot link our root CHANGELOG.md and do the same thing. We have package specific README.md files and a bump script that copies changelogs from each package in the MR to the masterchange log and runs apm pack --target all.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Given an mono-repo marketplace, comprised of many packages that have their own release numbers, what would be considered a best practice for expressing a github release within that github repo? Is it even necessary?
I'm looking at it as a sort of quick check that people can do when visiting the repo, but I suppose they can hot link our root CHANGELOG.md and do the same thing. We have package specific README.md files and a bump script that copies changelogs from each package in the MR to the masterchange log and runs
apm pack --target all.Beta Was this translation helpful? Give feedback.
All reactions