Skip to content
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

Add caller in the generation log #167

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

silvadenisaraujo
Copy link
Contributor

@silvadenisaraujo silvadenisaraujo commented Jan 21, 2025

In order to easily identify the caller of the generation I suggest we add the x-vtex-caller header that can be identification of an application or an user.

Example:
Pasted Graphic 3

Copy link
Contributor

vtex-io-ci-cd bot commented Jan 21, 2025

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@silvadenisaraujo silvadenisaraujo merged commit 39b2b0d into master Jan 30, 2025
5 checks passed
Copy link
Contributor

vtex-io-ci-cd bot commented Jan 30, 2025

Your PR has been merged! App is being published. 🚀
Version 2.16.5 → 2.16.6

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy [email protected]

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants