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

feat: add link to project after a push #208

Conversation

NicolasGirardot
Copy link
Contributor

Checklist

  • I have read the Contributor Guide
  • I have read and agree to the Code of Conduct
  • I have added a description of my changes and why I'd like them included in the section below

Description of Changes

Describe your changes here

Related Issues

List related issues here

@NicolasGirardot NicolasGirardot requested a review from a team as a code owner February 12, 2025 17:26
@@ -132,9 +132,12 @@ pub async fn run(opts: Options) -> anyhow::Result<()> {
.api_context("Could not create version")?;

tracing::info!(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@KokaKiwi is this actually logging to stdout? because I didn't get any confirmation message when pushing 🤔

maybe we should distinguish between tracing and standard logging?

manifest.package.name,
manifest.package.version,
organization.slug,
organization.slug,
manifest.package.name,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this ok to use in the URL? if we get the component slug in the API response, maybe that's a better way

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should use the component slug

Copy link
Contributor Author

@NicolasGirardot NicolasGirardot Feb 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm closing back the PR as we might be working with the return method of the update component based on another ticket

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