-
Notifications
You must be signed in to change notification settings - Fork 49
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 --only-templates
flag
#172
feat: add --only-templates
flag
#172
Conversation
Can we have instead of the --collapsedLinks option. |
What I'd like is something like this:
Maybe you can consider the comment has 2 sections. And let me activate sections and order them? For example And let me pass a custom section intro message for both. Full example CLI options: --section templates
--templates-intro 'This PR has been continuously released. You can run its code in one of our templates:'
--section dependencies
--dependencies-intro 'Alternatively you can try the PR code directly into your project:' |
2ae4060
to
af3bdd3
Compare
--only-templates
flag
Fine with a simple option 👍 |
let me know once it's on npm By the way what's the final comment with this new option? Is the comment template part of this repo? I may want to fork it and customize for our own needs eventually. |
For sure
Hmm, could you give me more context? Thank you so much❤️ |
Hmmm not sure what to add: we agreed to keep this option simple and not have the ability to provide custom labels like my former suggestion. Can I implement custom labels myself by forking/patching this package, or is the final message being created/posted by some StackBlitz internal backend? |
Oh yea, with the #183, now you can turn comments off, get the json output and then create your own message! 😄 We will release soon. |
@Aslemammad that probably works but looks more complicated, do you have a full github action example flow doing so? As far as I remember it's a bit annoying in terms of security to have your action post a GitHub comment and build the code. |
Yea, haven't looked into that, but for sure, it might have its own trade offs. But I guess that's only way we can make it extensible and let others custmize on top of it, without building many abstractions in code, which is a bit challenging. @pngwn might want to share thoughts on this? |
Yes we do this a lot over on gradio. It is indeed a little more annoying but relatively straightforward. I'll post an example flow shortly. |
Fwiw I do think the JSON approach is preferable to additional formatting params. This allow the most flexibility, and can even allow you to add the info to an existing CI reply rather than every service generating additional replies (which also gets very noisy). |
Yes JSON is flexible, now if you tell me how to wire it in my CI properly and I just have to copy/paste the complex actions files, that works for me 😄 |
Just waiting for a release and I'll post it (the old pr link is dead now). Has this been released? |
I'll also make a PR to the docs / readme when it is out. |
Hey not yet, we want to batch it with few other goodies and then!
Sorry for that.
…On Fri, Aug 23, 2024 at 5:12 PM pngwn ***@***.***> wrote:
I'll also make a PR to the docs / readme when it is out.
—
Reply to this email directly, view it on GitHub
<#172 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJBMICBOI6CBEYYUAD2YGJTZS433XAVCNFSM6AAAAABMRY7NYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBXGEZDGNZXGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No worries! |
For instance, check this PR in TanStack, TanStack/query#7861
The problem is when repository has too many packages the amount of scroll on the PR page will increase, adding another detail to the pkg.pr.new links conditional with a flag like
--collapsed-links
will help resolve this case