Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

docs: clarifycoder_metadata usage#267

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
ethanndickson merged 2 commits intomainfrom08-14-docs_clarify_coder_metadata_usage
Aug 29, 2024

Conversation

ethanndickson
Copy link
Member

@ethanndicksonethanndickson commentedAug 14, 2024
edited
Loading

Thecoder_metadata resource is only used to apply metadata to specific template resources. To apply metadata at the workspace level, and have it be shown on the main workspace pane, ametadata block needs to be created on thecoder_agent resource. Alternatively, anycoder_metadata attached to the resource containing the agent will be shown on the dashboard by default (see our dogfood template), but this isn't super obvious, so we'll add a comment.

It's pretty easy to assume that thecoder_metadata resource would let you apply workspace metadata, if you associated it with the agent, so we'll also add a comment mentioning this isn't the case.

matifali reacted with thumbs up emoji
@ethanndicksonGraphite App
Copy link
MemberAuthor

This stack of pull requests is managed by Graphite.Learn more about stacking.

Join@ethanndickson and the rest of your teammates onGraphiteGraphite

@ethanndicksonethanndickson marked this pull request as ready for reviewAugust 14, 2024 04:16
@ethanndicksonethanndicksonforce-pushed the08-14-docs_clarify_coder_metadata_usage branch from19dd470 to38546eaCompareAugust 14, 2024 04:17
@ethanndicksonethanndicksonforce-pushed the08-14-docs_clarify_coder_metadata_usage branch 2 times, most recently fromff7aabf to97e4fb5CompareAugust 14, 2024 05:30
@ethanndicksonethanndicksonforce-pushed the08-14-docs_clarify_coder_metadata_usage branch from97e4fb5 toca52f1fCompareAugust 14, 2024 05:48
@matifali
Copy link
Member

Important

We should backport this torelease/1.0 branch as themain currently has breaking changes.


Also, I renamed thev1-breaking milestone tov2 to track when we want to cut a 2.0 release.
cc:@stirby

Copy link
Member

@matifalimatifali left a comment
edited
Loading

Choose a reason for hiding this comment

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

@ethanndickson@stirby can you backport this to release branch too? And then we can push a new tag.

@ethanndicksonethanndickson merged commit286841d intomainAug 29, 2024
9 checks passed
@ethanndicksonethanndickson deleted the 08-14-docs_clarify_coder_metadata_usage branchAugust 29, 2024 04:14
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsAug 29, 2024
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@matifalimatifalimatifali approved these changes

@kylecarbskylecarbsAwaiting requested review from kylecarbs

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@ethanndickson@matifali

[8]ページ先頭

©2009-2025 Movatter.jp