Link to 'From GPL to Prompts' blog post added #198
Conversation
Added a link to the related blog post about Prompt Public License.
|
Caution Review failedThe pull request is closed. WalkthroughA blog post markdown file was updated to add an inline hyperlink reference to a related blog post about the Prompt Public License (PPL) within an existing narrative sentence, preserving surrounding content and context. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes
Poem
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to b2ec7e8 in 1 minute and 42 seconds. Click for details.
- Reviewed
14lines of code in1files - Skipped
0files when reviewing. - Skipped posting
1draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. jekyll/_posts/2025-12-03-when-english-hits-ring-0.md:55
- Draft comment:
The markdown link is split across two lines; please combine the link text and URL on one line to avoid potential rendering issues. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 15% vs. threshold = 50% The comment is about a formatting concern with a markdown link. While it's true the link spans two lines, this is actually valid markdown syntax and most parsers handle it correctly. The comment says "potential rendering issues" which is speculative - it's not definitively stating there IS a rendering issue. The rules say "Do NOT make speculative comments, such as 'If X, then Y is an issue', Only comment if it is definitely an issue." This comment uses "potential" which makes it speculative. Additionally, if there were actual rendering issues, that would likely be caught during the build/preview process. The rules also say "Do NOT comment on anything that would be obviously caught by the build." If this actually caused rendering problems, it would be visible in the rendered output. Maybe the author has experience with specific markdown parsers that do have issues with multi-line links? Perhaps there's a specific Jekyll configuration or markdown processor being used that doesn't handle this well? The comment could be based on real experience with rendering issues in this specific setup. Even if there were specific parser issues, the comment is phrased as "potential" issues, making it speculative rather than definitive. If the link actually breaks during rendering, that would be caught in the build or preview stage. The author clearly made this change intentionally (adding a long link), and if it rendered incorrectly, they would see it. Without evidence of an actual rendering problem, this is just a style preference being presented as a potential bug. This comment should be deleted. It's speculative ("potential rendering issues"), and multi-line markdown links are valid syntax that work correctly in standard markdown parsers including those used by Jekyll. Any actual rendering issues would be caught during build/preview.
Workflow ID: wflow_RyT4OPfeHhY4lwWR
You can customize 
There was a problem hiding this comment.
Pull request overview
This pull request adds a reference link to a related blog post about the Prompt Public License (PPL) within an existing article discussing PromptWare and software licensing.
- The change enhances the article by providing readers with a direct link to a detailed discussion of the PPL concept mentioned in the text
- The modification integrates contextual information about the author's licensing work into the narrative flow
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Which is how I ended up sketching a Prompt Public License (PPL, see my other blog post [From GPL to Prompts: Rethinking Open Source Licenses for the AI-Native Era | ||
| ](https://preangel.ai/2025/12/02/from-gpl-to-prompts/)) and then zooming out into the bigger question: |
There was a problem hiding this comment.
The markdown link has a line break in the middle of the link text. The opening bracket [ is on line 55, but the closing ] and URL are on line 56. This can cause rendering issues in some markdown parsers.
Consider reformatting to keep the link on a single line, or at least break after the link text:
Which is how I ended up sketching a Prompt Public License (PPL, see my other blog post
[From GPL to Prompts: Rethinking Open Source Licenses for the AI-Native Era](https://preangel.ai/2025/12/02/from-gpl-to-prompts/)) and then zooming out into the bigger question:Or keep it all on one line if line length permits:
Which is how I ended up sketching a Prompt Public License (PPL, see my other blog post [From GPL to Prompts: Rethinking Open Source Licenses for the AI-Native Era](https://preangel.ai/2025/12/02/from-gpl-to-prompts/)) and then zooming out into the bigger question:| Which is how I ended up sketching a Prompt Public License (PPL, see my other blog post [From GPL to Prompts: Rethinking Open Source Licenses for the AI-Native Era | |
| ](https://preangel.ai/2025/12/02/from-gpl-to-prompts/)) and then zooming out into the bigger question: | |
| Which is how I ended up sketching a Prompt Public License (PPL, see my other blog post [From GPL to Prompts: Rethinking Open Source Licenses for the AI-Native Era](https://preangel.ai/2025/12/02/from-gpl-to-prompts/)) and then zooming out into the bigger question: |
Added a link to the related blog post about Prompt Public License.
Please make sure to check the following boxes creating your pull request, thank you very much!
Add Blog Header, including title, author, image, categories, tags, etc.
For example:
Keep all filenames lowercase, and use
-to connect words instead of space. e.g.2017-10-06-wechat-pc-impactor.mdinstead of2017-10-06-WeChat PC Impactor.mdEmbed video/pdf from YouTube/Bilibili/local (if there's any) by using
{% include iframe.html src="URL_or_PATH" %}. (Learn more about how to embed file/url in the post by reading this blog postSave photo to local before publishing, to a folder named by
${MONTH}-${YOUR_BLOG_SLUG}/under/assets/2021/directory.Select a beautiful and meaningful teaser image for your blog
Create your contributor profile (if you are a first time contributor)
For excample:
Here is the example file:
To learn more about the contribute guideline, visit: https://wechaty.js.org/docs/contributor-program/
Important
Adds a link to a related blog post about the Prompt Public License in
2025-12-03-when-english-hits-ring-0.md.2025-12-03-when-english-hits-ring-0.mdto provide additional context on the Prompt Public License.This description was created by
for b2ec7e8. You can customize this summary. It will automatically update as commits are pushed.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.