Repository navigation
Agent/task 39 gf #3
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
Changes from all commits
6b55e37
6f3daa1
b3f12d9
e57dd94
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| 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 | ||||||||||
|
Comment on lines
+9
to
+14
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -eu
printf '%s\n' '--- workflow ---'
cat -n .github/workflows/update-readme.yml
printf '%s\n' '--- repository permission and workflow references ---'
rg -n --hidden -g '*.yml' -g '*.yaml' -g '!node_modules' 'permissions:|contents:|git push|actions/checkout|blog-post-workflow|github-activity-readme' .github README.md 2>/dev/null || true
printf '%s\n' '--- README markers ---'
rg -n -C 2 '<!--|BLOG|ACTIVITY|GITHUB|POST' README.md 2>/dev/null || trueRepository: dominicusin/dominicusin Length of output: 3545 🌐 Web query:
💡 Result: The GITHUB_TOKEN used in GitHub Actions is not inherently "write" by default; its permissions are determined by repository or organization-level settings [1][2]. Default Permissions - Modern GitHub repositories and organizations typically default to a "read-only" configuration for the GITHUB_TOKEN [2][3]. - When this default is active, any attempt to perform "write" operations (such as git push, creating releases, or commenting on issues) will fail with a 403 error ("Resource not accessible by integration") unless explicit permissions are granted [4][2]. - Repository administrators can configure these defaults under Settings > Actions > General > Workflow permissions [1][2]. How to Enable Write Permissions If your workflow requires write access (e.g., to push code or update repository contents), you must explicitly elevate the permissions within your workflow file using the Citations:
Declare If the repository or organization default token permission is read-only, 🤖 Prompt for AI AgentsSource: MCP tools There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔒 Security & Privacy | 🟠 Major | 🏗️ Heavy lift 🧩 Analysis chain🏁 Script executed: #!/usr/bin/env bash
set -euo pipefail
workflow=".github/workflows/update-readme.yml"
rg -n 'persist-credentials|GITHUB_TOKEN|gh_token|git push|remote set-url' "$workflow"Repository: dominicusin/dominicusin Length of output: 240 🏁 Script executed: #!/usr/bin/env bash
set -euo pipefail
workflow=".github/workflows/update-readme.yml"
cat -n "$workflow"
printf '\nRelevant references:\n'
rg -n -C 3 'checkout|GITHUB_TOKEN|git config|git push|permissions|pull_request|schedule|workflow_dispatch|concurrency' "$workflow"Repository: dominicusin/dominicusin Length of output: 2920 🌐 Web query:
💡 Result: In the actions/checkout action, the persist-credentials input defaults to true [1][2]. When enabled, this setting configures the local git environment with the authentication token (or SSH key) used during the checkout [3][4][5]. This persistence allows subsequent steps in the workflow to perform authenticated git operations—such as git fetch or git push—automatically, without requiring additional configuration [6][7]. The token is removed during the post-job cleanup phase to maintain security [3][4][5]. In newer versions (e.g., v6.0.0 and later), the credential storage location was updated to use a file under $RUNNER_TEMP instead of the local.git/config, which further improves security by preventing accidental leakage, such as through artifact uploads [7][8]. If you wish to prevent this behavior—for example, to restrict git access or use a different authentication method—you can explicitly set persist-credentials: false in your workflow step [3][6]. If persist-credentials is set to false, or if a later step alters the repository's remote configuration, subsequent git commands will not have access to the original token, which may result in authentication errors (such as a 403 Forbidden) if those steps attempt to perform remote git operations [6]. Citations:
Disable checkout credential persistence
🧰 Tools🪛 zizmor (1.29.0)[warning] 14-16: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false (artipacked) 🤖 Prompt for AI AgentsSources: MCP tools, Linters/SAST tools |
||||||||||
|
|
||||||||||
| # Обновление статистики GitHub (языки, общая статистика) | ||||||||||
| - name: Generate GitHub Stats | ||||||||||
| uses: jamesgeorge007/github-activity-readme@master | ||||||||||
| env: | ||||||||||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||||||||||
|
Comment on lines
+17
to
+20
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 2. Unpinned github action The workflow uses jamesgeorge007/github-activity-readme@master, which is a mutable ref; this reduces reproducibility and increases supply-chain risk because the executed code can change without a review in this repo. Agent Prompt
Comment on lines
+16
to
+20
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🏁 Script executed: #!/usr/bin/env bash
set -euo pipefail
for marker in '<!--START_SECTION:activity-->' '<!--END_SECTION:activity-->'; do
grep -nF "$marker" README.md
doneRepository: dominicusin/dominicusin Length of output: 161 🏁 Script executed: #!/usr/bin/env bash
set -euo pipefail
printf '%s\n' '--- workflow ---'
cat -n .github/workflows/update-readme.yml
printf '%s\n' '--- README marker and stats references ---'
rg -n -C 3 'activity|github-activity|github-readme-stats|START_SECTION|END_SECTION|BLOG' README.md || true
printf '%s\n' '--- repository files relevant to README generation ---'
git ls-files | rg '(^|/)(README\.md|update-readme\.yml)$|github|workflow' | head -100Repository: dominicusin/dominicusin Length of output: 3297 🌐 Web query:
💡 Result: The jamesgeorge007/github-activity-readme GitHub Action uses HTML comment tags in your README.md file as markers to identify where to inject or update activity content [1][2]. The specific markers used are and [3][4]. When the workflow runs, it behaves as follows: 1. Entry Point: The action searches for the comment within the target file (defaulting to README.md) [1][2][5]. 2. Replacement Strategy: The action replaces all existing content located between the start and end markers with the newly fetched GitHub activity [6]. This ensures that the generated activity block remains up-to-date and avoids appending duplicate information [6]. 3. Generation Limits: The number of activity lines displayed is controlled by the MAX_LINES input parameter (defaulting to 5) [2][5]. 4. Git Integration: Because the action modifies the README file, it attempts to commit and push the changes back to your repository [6]. If there are no actual changes between the previous and newly generated content, no new commit is created, leveraging Git as the primary mechanism for detecting and managing content changes [6]. To implement this, you simply need to add these markers to your README file and configure the workflow in your.github/workflows directory [1][4]. The action then populates the space between these tags with your recent public GitHub activity [1][3]. Citations:
Replace the activity action or add its required markers.
🤖 Prompt for AI AgentsSource: MCP tools |
||||||||||
|
|
||||||||||
| # Обновление последних постов блога | ||||||||||
| - name: Update blog posts | ||||||||||
| uses: gautamkrishnar/blog-post-workflow@v1 | ||||||||||
|
Comment on lines
+14
to
+24
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔒 Security & Privacy | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🏁 Script executed: #!/usr/bin/env bash
set -euo pipefail
workflow=".github/workflows/update-readme.yml"
if rg -nP '^\s*-\s*uses:\s+\S+@(?:master|main|v\d+(?:\.\d+)*)\s*$' "$workflow"; then
echo "Mutable action reference found" >&2
exit 1
fiRepository: dominicusin/dominicusin Length of output: 229 🏁 Script executed: #!/usr/bin/env bash
set -euo pipefail
workflow=".github/workflows/update-readme.yml"
printf '%s\n' '--- workflow action references and permissions ---'
cat -n "$workflow"
printf '%s\n' '--- all uses references ---'
rg -n '^\s*uses:\s+' "$workflow"
printf '%s\n' '--- repository action references ---'
git ls-files '.github/workflows/update-readme.yml'Repository: dominicusin/dominicusin Length of output: 2065 🏁 Script executed: #!/usr/bin/env bash
set -euo pipefail
for ref in \
"https://github.com/actions/checkout.git refs/tags/v4" \
"https://github.com/jamesgeorge007/github-activity-readme.git refs/heads/master" \
"https://github.com/gautamkrishnar/blog-post-workflow.git refs/tags/v1"
do
repo="${ref% refs/*}"
git_ref="${ref#* }"
printf '%s -> ' "$repo $git_ref"
git ls-remote "$repo" "$git_ref" | awk '{print $1}'
doneRepository: dominicusin/dominicusin Length of output: 495 🏁 Script executed: #!/usr/bin/env bash
set -euo pipefail
resolve_tag() {
local repo="$1" tag="$2"
printf '%s %s\n' "$repo" "$tag"
git ls-remote "$repo" "refs/tags/$tag" "refs/tags/$tag^{}"
}
resolve_tag https://github.com/actions/checkout.git v4
resolve_tag https://github.com/gautamkrishnar/blog-post-workflow.git v1
for item in \
"actions/checkout 11d5960a326750d5838078e36cf38b85af677262" \
"jamesgeorge007/github-activity-readme 4aefbfa1c222d70537dc6a02f0519266aab2b1ea" \
"gautamkrishnar/blog-post-workflow 8fe00f11b147770bd95a8e1c41f4d033c3929b5f"
do
repo="${item% *}"
sha="${item##* }"
printf '%s ' "$repo"
git ls-remote "https://github.com/$repo.git" "$sha"
doneRepository: dominicusin/dominicusin Length of output: 518 Pin all action references to audited commit SHAs. Replace 🧰 Tools🪛 zizmor (1.29.0)[warning] 14-16: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false (artipacked) 🤖 Prompt for AI AgentsSource: MCP tools |
||||||||||
| 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" | ||||||||||
|
Comment on lines
+23
to
+27
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🏁 Script executed: #!/bin/bash
printf '%s\n' '--- workflow ---'
cat -n .github/workflows/update-readme.yml
printf '%s\n' '--- README markers and blog entries ---'
rg -n -C 4 'BLOG|blog|Latest|202[0-9]|20[0-9][0-9]' README.md
printf '%s\n' '--- repository files relevant to workflow ---'
git ls-files '.github/workflows/update-readme.yml' 'README.md'Repository: dominicusin/dominicusin Length of output: 6620 🌐 Web query:
💡 Result: In the gautamkrishnar/blog-post-workflow GitHub Action, the requested parameters are used to customize how blog posts are rendered in your README [1][2]. Here is a breakdown of their functions: date_format Default: UTC:ddd mmm dd yyyy h:MM TT [1][2] Purpose: Allows you to define the format of the date or time displayed when using the $date variable in your template [1][2]. This option utilizes the NPM dateformat library [1]. $description Purpose: A supported variable used within the template option that inserts the description of the post [1]. $newline Purpose: A supported variable used within the template option that inserts a newline [1][2]. comment_tag_name Purpose: This parameter allows you to override the default comment tag name [2]. It is primarily used if you need to run multiple instances of the blog-post-workflow action on the same repository [2]. By specifying a unique comment_tag_name for each instance, you prevent them from overwriting each other's output sections in your README file. Citations:
🏁 Script executed: #!/bin/bash
set -e
curl -fsSL https://raw.githubusercontent.com/gautamkrishnar/blog-post-workflow/master/action.yml |
sed -n '1,180p'
printf '%s\n' '--- README documentation ---'
curl -fsSL https://raw.githubusercontent.com/gautamkrishnar/blog-post-workflow/master/README.md |
rg -n -C 4 'template|date_format|comment_tag_name|BLOG-POST-LIST|description|\$newline'Repository: dominicusin/dominicusin Length of output: 50381 🏁 Script executed: #!/bin/bash
set -e
curl -fsSL https://raw.githubusercontent.com/gautamkrishnar/blog-post-workflow/master/dist/blog-post-workflow.js |
rg -n -C 3 'template ===|template.*default|default.*template|description|date_format|BLOG-POST-LIST' |
head -n 120Repository: dominicusin/dominicusin Length of output: 4915 Preserve the existing blog entry format. Remove the 🤖 Prompt for AI AgentsSource: MCP tools There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -u
printf '%s\n' '--- workflow ---'
cat -n .github/workflows/update-readme.yml | sed -n '20,32p'
printf '%s\n' '--- feed status ---'
for url in \
'https://dominicusin.github.io/feed.xml' \
'https://dominicusin.github.io/rss.xml' \
'https://dominicusin.github.io/atom.xml'
do
curl -L --silent --show-error --max-time 20 \
-o /dev/null -w '%{http_code} %{url_effective} %\n' "$url" || true
done
printf '%s\n' '--- referenced action ---'
rg -n -C 3 'blog-post-workflow|feed_list' .github README.md 2>/dev/null || trueRepository: dominicusin/dominicusin Length of output: 1803 🏁 Script executed: #!/bin/bash
set -u
tmpdir="$(mktemp -d)"
trap 'rm -rf "$tmpdir"' EXIT
curl -L --fail --silent --show-error \
https://api.github.com/repos/gautamkrishnar/blog-post-workflow/git/trees/master?recursive=1 \
-o "$tmpdir/tree.json"
python3 - "$tmpdir/tree.json" <<'PY'
import json, sys
tree = json.load(open(sys.argv[1]))
for item in tree.get("tree", []):
path = item.get("path", "")
if path.endswith((".js", ".ts", ".yml", ".yaml")) and any(
term in path.lower() for term in ("index", "feed", "action")
):
print(path)
PY
printf '%s\n' '--- feed/error handling references ---'
curl -L --fail --silent --show-error \
https://api.github.com/repos/gautamkrishnar/blog-post-workflow/git/trees/master?recursive=1 |
python3 -c '
import json,sys
for x in json.load(sys.stdin).get("tree",[]):
if x.get("type")=="blob" and x["path"].endswith((".js",".ts",".yml",".yaml",".json")):
print(x["path"])
' |
while IFS= read -r path; do
content="$(curl -L --fail --silent --show-error "https://raw.githubusercontent.com/gautamkrishnar/blog-post-workflow/master/$path" 2>/dev/null || true)"
if printf '%s' "$content" | grep -Eiq 'feed_list|feed|reject|throw|process\.exit|failed|error'; then
printf '%s\n' "--- $path"
printf '%s\n' "$content" | grep -Ein -C 3 'feed_list|reject|throw|process\.exit|failed|error' | head -120
fi
doneRepository: dominicusin/dominicusin Length of output: 1065 🌐 Web query:
💡 Result: When the gautamkrishnar/blog-post-workflow action encounters an issue retrieving an RSS feed, resulting in an error (such as a 404, 429, or other non-200 status codes), it indicates that the workflow cannot successfully crawl the provided URL [1][2]. The official documentation and common troubleshooting guidance from the action author specify that this is typically caused by one of the following factors [1][2]: 1. Invalid URL: The URL provided in the feed_list option may be incorrect or inaccessible [1][2]. 2. Blocking by Hosting Provider: Your website’s hosting or DNS provider may be blocking requests originating from GitHub IP addresses, often to prevent spam or DDoS attacks [1][2]. 3. Security Challenges: Some hosting environments (e.g., Vercel security checkpoints) may inject browser verification challenges that prevent automated tools from accessing the feed, often resulting in 429 errors [3]. Recommended troubleshooting steps: - Verify the URL: Ensure the feed URL is correct and directly accessible in your browser [1][2]. - Test with Debugging Tools: Use the tmate debugging action to establish an SSH connection with the GitHub runner [1][2]. From the runner, execute the command curl -I to see the exact HTTP response code the runner receives [1][2]. - Contact Hosting Support: If the runner receives a non-200 status code (such as 403, 404, or 429), the issue lies with your server's configuration or security filtering. You may need to contact your hosting or CDN provider to ensure they are not blocking GitHub's crawlers [1][2]. For additional context, users of this action must also ensure that the actions/checkout step is included in their workflow, as missing this step is a common cause of failures in the action's execution [4]. Citations:
Remove the dead feed endpoints.
🤖 Prompt for AI AgentsSource: MCP tools |
||||||||||
| commit_msg: "Update latest blog posts in README" | ||||||||||
| comment_tag_name: "BLOGPOSTS" | ||||||||||
|
Comment on lines
+26
to
+29
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 1. Blog tag mismatch .github/workflows/update-readme.yml configures blog-post-workflow to update markers named BLOGPOSTS, but README.md contains BLOG-POST-LIST markers, so the workflow will not update the intended README section. Agent Prompt
Comment on lines
+28
to
+29
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -eu
printf '%s\n' '--- workflow files ---'
git ls-files '.github/workflows/update-readme.yml' 'README.md'
printf '%s\n' '--- workflow ---'
cat -n .github/workflows/update-readme.yml
printf '%s\n' '--- README markers ---'
rg -n -C 3 'BLOG[-_]POST|BLOGPOST|blog' README.md || true
printf '%s\n' '--- action references and input names ---'
rg -n -C 3 'blog-post-workflow|commit_msg|commit_message|comment_tag_name' .Repository: dominicusin/dominicusin Length of output: 4881 🏁 Script executed: #!/bin/bash
set -eu
tmpdir="$(mktemp -d)"
trap 'rm -rf "$tmpdir"' EXIT
curl -fsSL https://raw.githubusercontent.com/gautamkrishnar/blog-post-workflow/master/action.yml \
-o "$tmpdir/action.yml"
curl -fsSL https://raw.githubusercontent.com/gautamkrishnar/blog-post-workflow/master/README.md \
-o "$tmpdir/README.md"
curl -fsSL https://api.github.com/repos/gautamkrishnar/blog-post-workflow/git/trees/v1?recursive=1 \
-o "$tmpdir/tree.json"
printf '%s\n' '--- action inputs ---'
sed -n '/inputs:/,$p' "$tmpdir/action.yml" | head -80
printf '%s\n' '--- documented input names and marker behavior ---'
rg -n -C 3 'commit_message|commit_msg|comment_tag_name|BLOG-POST-LIST|not found|marker|tag' \
"$tmpdir/README.md" "$tmpdir/action.yml" || true
printf '%s\n' '--- v1 source files ---'
jq -r '.tree[] | select(.type == "blob") | .path' "$tmpdir/tree.json" \
| rg '(^|/)(index|main|src/).*\.(js|ts)$|action\.yml$' || trueRepository: dominicusin/dominicusin Length of output: 212 🌐 Web query:
💡 Result: The "blog-post-workflow" GitHub Action by gautamkrishnar uses specific HTML comment tags in your README to identify where it should insert or update content [1]. By default, the action looks for the following markers in your README.md file: If you receive an error related to a "missing marker" or if the action fails to update your README, it is likely because: 1. The markers are missing: Ensure both the:START and:END tags are present in your README exactly as shown above [1]. 2. Custom tag mismatch: If you have overridden the default tag name using the Citations:
🏁 Script executed: #!/bin/bash
set -eu
tmpdir="$(mktemp -d)"
trap 'rm -rf "$tmpdir"' EXIT
for url in \
'https://www.gitmemories.com/gautamkrishnar/blog-post-workflow' \
'https://raw.githubusercontent.com/gautamkrishnar/blog-post-workflow/v1/action.yml' \
'https://raw.githubusercontent.com/gautamkrishnar/blog-post-workflow/master/action.yml' \
'https://raw.githubusercontent.com/gautamkrishnar/blog-post-workflow/master/README.md'
do
printf '\n--- %s ---\n' "$url"
curl -LfsS --max-time 20 "$url" 2>/dev/null \
| rg -n -C 2 'commit_message|commit_msg|comment_tag_name|BLOG-POST-LIST' \
| head -100 || true
doneRepository: dominicusin/dominicusin Length of output: 27399 Use the declared blog action inputs and marker value.
Proposed fix- commit_msg: "Update latest blog posts in README"
- comment_tag_name: "BLOGPOSTS"
+ commit_message: "Update latest blog posts in README"
+ comment_tag_name: "BLOG-POST-LIST"📝 Committable suggestion
Suggested change
🤖 Prompt for AI AgentsSource: MCP 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 | ||||||||||
| else | ||||||||||
| echo "No changes to commit" | ||||||||||
| fi | ||||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,2 +1,72 @@ | ||
| ``` | ||
| # Dependencies | ||
|
Comment on lines
+1
to
+2
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 3. Stray gitignore backticks .gitignore contains literal Markdown code-fence lines (```), which Git treats as ignore patterns (not formatting) and makes the ignore file confusing to maintain. Agent Prompt
|
||
| node_modules/ | ||
| .venv/ | ||
| venv/ | ||
| __pycache__/ | ||
| .mypy_cache/ | ||
| .pytest_cache/ | ||
| dist/ | ||
| build/ | ||
| target/ | ||
| .gradle/ | ||
|
|
||
| # Logs and temp files | ||
| *.log | ||
| *.tmp | ||
| *.swp | ||
| *.swo | ||
|
|
||
| # Environment | ||
| .env | ||
| .env.local | ||
| *.env.* | ||
|
|
||
| # Editors | ||
| .vscode/ | ||
| .idea/ | ||
|
|
||
| # System files | ||
| .DS_Store | ||
| Thumbs.db | ||
|
|
||
| # Compiled files | ||
| *.pyc | ||
| *.class | ||
| *.o | ||
| *.exe | ||
| *.dll | ||
| *.so | ||
| *.a | ||
| *.obj | ||
| *.out | ||
|
|
||
| # Coverage | ||
| coverage/ | ||
| htmlcov/ | ||
| .coverage | ||
|
|
||
| # 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 | ||
| ``` | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: dominicusin/dominicusin
Length of output: 161
🏁 Script executed:
Repository: dominicusin/dominicusin
Length of output: 2365
🌐 Web query:
GitHub Actions concurrency cancel-in-progress false workflow-level overlapping runs pending queue behavior💡 Result:
In GitHub Actions, setting
cancel-in-progress: false(the default) does not mean that all triggered workflows will execute. It specifically governs the behavior of currently running jobs, not the behavior of the pending queue [1][2]. The behavior of the pending queue whencancel-in-progress: falseis configured depends on thequeueproperty [3][4]: 1. Default Behavior (queue: single): By default, a concurrency group can have at most one job or workflow in progress and at most one job or workflow in thependingstate [3][5]. If a new run is triggered while another is alreadypending, the existingpendingrun is automatically canceled to make room for the newer run [6][3]. Consequently, even withcancel-in-progress: false, if multiple runs are triggered in rapid succession, older pending runs will be dropped [2][5]. 2. Queuing Behavior (queue: max): As of May 2026, you can enable a larger queue by settingqueue: max[7]. This allows up to 100 jobs or workflows to wait in thependingstate within the same concurrency group [3][8]. When this is enabled, runs are processed sequentially without being canceled [3][7]. Crucially,queue: maxcannot be used in combination withcancel-in-progress: truebecause they represent conflicting strategies for handling new runs [6][3]. In summary, if you need every run to execute without being dropped, you must usequeue: max; using onlycancel-in-progress: falsewill still result in the cancellation of older pending runs if a newer one enters the queue [2][7].Citations:
🌐 Web query:
jamesgeorge007/github-activity-readme action commits pushes README blog-post-workflow commit_msg behavior💡 Result:
The jamesgeorge007/github-activity-readme GitHub Action updates a specified file (defaulting to README.md) with your recent GitHub activity [1][2]. The action functions by finding a designated comment section within the target file (typically marked by start and end tags) and replacing the content between them [1][3]. Regarding your specific questions on behavior: Commit and Push Behavior: The action performs a commit and push to your repository when it detects changes to the activity list [1][3]. It uses standard Git operations to manage these updates [3]. If there are no changes to the activity, no new commit or push will typically occur [3]. Commit Message Configuration: - Standard Commit: You can customize the message used for standard updates by setting the COMMIT_MSG input parameter [1][2]. The default value is ":zap: Update README with the recent activity" [1][2]. - Empty Commit: If there are no updates to list, the action can use a different commit message, configurable via the EMPTY_COMMIT_MSG parameter [1][2]. The default for this is ":memo: empty commit to keep workflow active after 60 days of no activity" [1][2]. Workflow Integration: To use the action, you must include it in your GitHub workflow YAML file [1][4]. It requires the actions/checkout action to run first, and the GITHUB_TOKEN environment variable must be provided to allow the action to commit changes back to your repository [1][4][5]. You can override default behaviors like the committer name (COMMIT_NAME), committer email (COMMIT_EMAIL), the maximum number of lines (MAX_LINES), and the specific events to track (FILTER_EVENTS) through the action's input parameters [1][2].
Citations:
v0.5.0jamesgeorge007/github-activity-readme#102🌐 Web query:
gautamkrishnar/blog-post-workflow GitHub Action commit push behavior commit_msg💡 Result:
In the gautamkrishnar/blog-post-workflow GitHub Action, the commit_message input allows you to customize the commit message used when the action updates your README with new blog posts [1][2]. Regarding its commit and push behavior: Commit Message Customization: You can set the commit_message input in your workflow YAML file to a string of your choice. If not specified, it defaults to Updated with the latest blog posts [1][2]. Automatic Commits: By default, the action automatically commits and pushes the changes made to your README file back to your repository [1]. Skipping Commits: If you wish to prevent the action from creating a new commit, you can set the skip_commit input to true. Note that even with skip_commit set to true, the action will still modify the README file; this option is primarily for users who prefer to handle the commits manually via the Git CLI or another workflow [1][2]. Keepalive Commits: The action includes a feature that performs dummy commits to keep the repository active, which is particularly useful for cron-triggered workflows [1]. You can customize the message for these specific commits using the dummy_commit_message input (which defaults to dummy commit to keep the repository active, see https://git.io/Jtm4V) or disable the keepalive functionality entirely using the enable_keepalive input [1][3].
Citations:
🌐 Web query:
GitHub Actions concurrency queue max syntax 2026 workflow-level concurrency💡 Result:
As of August 2026, GitHub Actions supports an optional
queueproperty within the workflow-levelconcurrencyconfiguration to manage pending workflow runs [1][2]. Thequeueproperty supports the following values: -single(default): At most one job or workflow run can bependingin the concurrency group [1][3]. When a new run is queued, any existingpendingrun in the same group is canceled and replaced [1][2]. -max: Allows up to 100 jobs or workflow runs to bependingin the concurrency group [1][4]. When the queue reaches this limit, any additional incoming jobs or workflow runs are canceled [1][3]. Example usage: concurrency: group: production-deploy queue: max Important considerations: - Thequeue: maxoption cannot be used in combination withcancel-in-progress: true[1][5]. Configuring both will result in a workflow validation error because they represent conflicting behaviors regarding how in-progress runs are handled [1][3]. - When usingqueue: max, jobs or workflow runs are processed sequentially based on the order in which they began waiting in the concurrency group [1]. This feature was introduced to allow for larger, sequential queues, providing better control for deployments and resources requiring orderly execution [2].Citations:
Serialize scheduled and manual runs.
Both external actions and the final step can commit or push
README.md. Add a workflow-levelconcurrencygroup withcancel-in-progress: falseto prevent concurrent updates. Setqueue: maxif every triggered run must execute.🤖 Prompt for AI Agents
Source: MCP tools