Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions .github/workflows/update-readme.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
name: Update README Stats & Blog Posts

on:
schedule:
# Запуск каждый день в 00:00 UTC
- cron: "0 0 * * *"
workflow_dispatch: # Возможность ручного запуска

jobs:
build:
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v4

# Обновление статистики GitHub (языки, общая статистика)
- name: Generate GitHub Stats
uses: jamesgeorge007/github-activity-readme@master
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Comment on lines +17 to +20

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remediation recommended

2. Unpinned action reference 🐞 Bug ⛨ Security

The workflow uses jamesgeorge007/github-activity-readme@master, which is a mutable branch
reference; upstream changes can silently change CI behavior and increase supply-chain risk.
Agent Prompt
### Issue description
Using an action via a moving branch (`@master`) makes builds non-reproducible and increases supply-chain risk because the referenced code can change without any change in this repo.

### Issue Context
The workflow runs on a schedule and can modify repository contents, so deterministic and reviewable action versions are important.

### Fix Focus Areas
- .github/workflows/update-readme.yml[16-21]

### Suggested fix
Replace `@master` with an immutable reference:
- Prefer pinning to a full commit SHA (recommended), optionally with a comment noting the release version.
- Alternatively pin to a specific release tag if the action guarantees immutability.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Comment on lines +16 to +20

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Informational

5. Stats step likely ineffective 🐞 Bug ⚙ Maintainability

The workflow’s "Generate GitHub Stats" step uses github-activity-readme, but README.md contains no
activity section markers for that action, so this step is likely a no-op (or may fail depending on
action behavior).
Agent Prompt
### Issue description
The workflow adds a step using `jamesgeorge007/github-activity-readme`, but the README does not include an obvious marker block for that action, so the step likely won’t update the README as intended.

### Issue Context
README already includes stats via images, and contains only the blog-post marker block.

### Fix Focus Areas
- .github/workflows/update-readme.yml[16-21]
- README.md[1-35]
- README.md[83-99]

### Suggested fix
Either:
- Add the action’s expected marker block to README (per the action’s conventions), or
- Remove/replace this step if you only want the existing image-based stats and the blog-post updates.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


# Обновление последних постов блога
- name: Update blog posts
uses: gautamkrishnar/blog-post-workflow@v1
with:
max_post_count: "5"
feed_list: "https://dominicusin.github.io/feed.xml,https://dominicusin.github.io/rss.xml,https://dominicusin.github.io/atom.xml"
commit_msg: "Update latest blog posts in README"
comment_tag_name: "BLOGPOSTS"

Comment on lines +26 to +30

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Action required

1. Blog tag mismatch 🐞 Bug ≡ Correctness

The blog-post workflow is configured to look for the tag "BLOGPOSTS", but README.md contains
"BLOG-POST-LIST" markers, so the action will not find the replacement block and will not update the
blog posts section.
Agent Prompt
### Issue description
`gautamkrishnar/blog-post-workflow` updates README by replacing content between `<!-- <TAG>:START -->` and `<!-- <TAG>:END -->`. The workflow sets `comment_tag_name: "BLOGPOSTS"`, but the README uses `BLOG-POST-LIST`, so updates never apply.

### Issue Context
- Workflow sets the tag name to `BLOGPOSTS`.
- README markers are `BLOG-POST-LIST`.

### Fix Focus Areas
- .github/workflows/update-readme.yml[23-30]
- README.md[83-97]

### Suggested fix
Choose one:
1) Remove `comment_tag_name` entirely (use default markers), or
2) Set `comment_tag_name: "BLOG-POST-LIST"`, or
3) Rename README markers to `<!-- BLOGPOSTS:START -->` / `<!-- BLOGPOSTS:END -->` to match the workflow.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

# Коммит и пуш изменений
- name: Commit & Push changes
run: |
git config user.name github-actions
git config user.email github-actions@github.com
if [[ $(git status --porcelain) != "" ]]; then
git add README.md
git commit -m "chore: auto-update stats and blog posts"
git push
Comment on lines +36 to +39

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remediation recommended

3. Implicit token permissions 🐞 Bug ☼ Reliability

The workflow performs git push but does not declare permissions: contents: write, so in
repos/orgs where the default GITHUB_TOKEN is read-only, scheduled runs will fail to push README
updates.
Agent Prompt
### Issue description
The workflow pushes commits back to the repository. Without explicitly declaring `permissions: contents: write`, the job may fail under common GitHub configurations where the default GITHUB_TOKEN is read-only for repository contents.

### Issue Context
This job is scheduled and intended to auto-commit changes, so it should be self-contained and not depend on repository-level default token permissions.

### Fix Focus Areas
- .github/workflows/update-readme.yml[1-12]
- .github/workflows/update-readme.yml[31-40]

### Suggested fix
Add at workflow (top) or job level:
```yaml
permissions:
  contents: write
```
Keep the existing push logic as-is.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

else
echo "No changes to commit"
fi
61 changes: 61 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,2 +1,63 @@
```
# Dependencies
node_modules/
Comment on lines +1 to 3

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remediation recommended

4. Gitignore code fences 🐞 Bug ⚙ Maintainability

The .gitignore file now contains Markdown code-fence lines (```), which are treated as literal
ignore patterns and make the ignore file misleading/confusing.
Agent Prompt
### Issue description
Markdown code fences are not valid `.gitignore` syntax; they become literal ignore patterns and create confusion about what is actually ignored.

### Issue Context
The first and last lines of `.gitignore` are triple backticks.

### Fix Focus Areas
- .gitignore[1-3]
- .gitignore[61-63]

### Suggested fix
Delete the opening and closing ``` lines and ensure the file ends with a newline.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


# Editors
.vscode/

# Environment
.env
.env.local
.env.*

# Logs and temp files
*.log
*.tmp
*.swp

# Build artifacts
dist/
build/
*.pyc
__pycache__/
*.o
*.obj

# Coverage reports
coverage/
htmlcov/
.coverage

# Python specific
*.pyc
*.pyo
*.pyd
.Python
*.so
*.egg-info/
.eggs/

# Compressed files
*.zip
*.gz
*.tar
*.tgz
*.bz2
*.xz
*.7z
*.rar
*.zst
*.lz4
*.lzh
*.cab
*.arj
*.rpm
*.deb
*.Z
*.lz
*.lzo
*.tar.gz
*.tar.bz2
*.tar.xz
*.tar.zst
```
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,7 @@ I develop, experiment with tools and infrastructure, and share my findings on my

## 📰 Latest blog posts

<!-- BLOG-POST-LIST:START -->
- **[YA movies's list](https://dominicusin.github.io/2025/11/yet-another-list-of-movies/)** — *Nov 2, 2025*
Curated collection of films including "Greener Grass" (2019), "Mulholland Dr." (2001), "Se7en" (1995), and others spanning diverse genres and artistic styles.

Expand All @@ -93,6 +94,7 @@ I develop, experiment with tools and infrastructure, and share my findings on my

- **[λογική (Logiki)](https://dominicusin.github.io/2025/10/logiki/)** — *Oct 14, 2025*
Comprehensive examination of multiple logical systems beyond classical deduction, including abductive, dialectical, and fuzzy logic approaches adapted to various domains.
<!-- BLOG-POST-LIST:END -->

---

Expand Down