-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MM-33506] Use embed package to include plugin manifest #145
Conversation
Please note that CI is expected to fail until the orb is updated to go1.16. |
github.com/kr/text v0.2.0 // indirect | ||
github.com/mattermost/mattermost-server/v5 v5.26.2 | ||
github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e // indirect | ||
github.com/mattermost/mattermost-server/v5 v5.32.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I piggy backed a dependency update into this PR
@@ -0,0 +1,17 @@ | |||
package root |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Naming is hard. I thought about using manifest
but manifest.Manifest
would stutter. Ideas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only adding a brief comment, since we diverged somewhat in incident collaboration in a way that I think requires keeping the apply
target in some fashion (to auto-populate the version field). cc @cpoile for review
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! LGTM
Looks like the typescript linter is failing
|
@lieut-data As long as we don't expect to be able to merge the starter-template with Even if we change circle-ci so that it doesn't require or call |
@DHaussermann Would you be fine if I merge this PR without QA review as it's purely tooling related? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @hanzei
This PR is okay to merge without functional testing.
This reverts commit ca9ee3c.
#192) * Revert "Update main.go (#154)" This reverts commit be4a281. * Revert "[MM-33506] Use embed package to include plugin manifest (#145)" This reverts commit ca9ee3c. * Revert "Don't generate manifest.ts (#127)" This reverts commit 18d30b5. * install-go-tools target, adopt gotestsum * bring back make apply + automatic versioning * Update build/manifest/main.go Co-authored-by: Michael Kochell <6913320+mickmister@users.noreply.github.com> * suppress git describe error when no tags match * make version/release notes opt-in * fix whitespace in Makefile * document version management options --------- Co-authored-by: Michael Kochell <6913320+mickmister@users.noreply.github.com>
Summary
Instead of generating a
manifest.go
file the code makes use of the new embed feature of go1.16 to embed the manifest directly. This drops the last generated file from the repo and makes the developers live easier. I leavedmake apply
intentionally as a command in case someone runs it from old habits or some script is still using it.Ticket Link
https://mattermost.atlassian.net/browse/MM-33506