Seed content: About, Projects, and draft blog posts #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reviewer's GuideThis PR populates the Jekyll site with foundational content, enhances developer documentation for local and draft workflows, and adds automation and architecture guidance. Changes are implemented by adding and updating markdown files for pages and posts, extending the README, and introducing new workflow/configuration files. Class diagram for new and updated content types (Pages, Posts, Drafts)classDiagram
class Page {
+title: string
+layout: string
+permalink: string
+content: markdown
}
class Post {
+title: string
+date: datetime
+author: string
+tags: list
+content: markdown
}
class Draft {
+title: string
+author: string
+tags: list
+content: markdown
}
Page <|-- AboutPage
Page <|-- ProjectsPage
Post <|-- WelcomePost
Draft <|-- SymbolicRecursionDraft
Draft <|-- RecursiveReasoningLLMDraft
Draft <|-- MindRecursiveSystemsDraft
Draft <|-- CaseStudyEmergentRecursionDraft
AboutPage : updated content
ProjectsPage : new page
WelcomePost : new post
SymbolicRecursionDraft : new draft
RecursiveReasoningLLMDraft : new draft
MindRecursiveSystemsDraft : new draft
CaseStudyEmergentRecursionDraft : new draft
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey there - I've reviewed your changes and they look great!
Blocking issues:
- An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. (link)
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location> `.github/workflows/jekyll-build.yml:32-33` </location>
<code_context>
+ - name: Upload site (artifact)
+ uses: actions/upload-artifact@v4
+ with:
+ name: site
+ path: _site
</code_context>
<issue_to_address>
**suggestion:** Consider cleaning up the _site directory before building to avoid stale artifacts.
This helps ensure only fresh build files are uploaded, reducing the risk of outdated content in the artifact.
</issue_to_address>
### Comment 2
<location> `.github/workflows/jekyll-build.yml:16` </location>
<code_context>
uses: ruby/setup-ruby@v1
</code_context>
<issue_to_address>
**security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha):** An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
*Source: opengrep*
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Comment on lines
+32
to
+33
| name: site | ||
| path: _site |
There was a problem hiding this comment.
suggestion: Consider cleaning up the _site directory before building to avoid stale artifacts.
This helps ensure only fresh build files are uploaded, reducing the risk of outdated content in the artifact.
| - uses: actions/checkout@v4 | ||
|
|
||
| - name: Set up Ruby | ||
| uses: ruby/setup-ruby@v1 |
There was a problem hiding this comment.
security (yaml.github-actions.security.third-party-action-not-pinned-to-commit-sha): An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
Source: opengrep
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR seeds the site with:\n\n- Revised About page reflecting Recursion Lab’s focus\n- New Projects page with four prototype ideas\n- Four draft blog posts under _drafts/ (symbolic recursion, recursive reasoning in LLMs, mind–recursive systems interface, case study)\n- README note on using _drafts and serving with --drafts\n\nBuild: Verified locally with bundle exec jekyll build (non-blocking Sass deprecations remain from vendor files).\n\nYou can replace or expand these sections with your own content at any time.\n
Summary by Sourcery
Seed the site with core content pages, draft posts, and a welcome post, improve developer documentation for local and draft workflows, and introduce a CI workflow for automated Jekyll builds.
New Features:
CI:
Documentation: