Skip to content

chore: ci bump (fixes #1168)#1259

Open
mirkosalvato1-ctrl wants to merge 1 commit into
codeaashu:mainfrom
mirkosalvato1-ctrl:oslifeguard/ci_bump-1168-1784789047
Open

chore: ci bump (fixes #1168)#1259
mirkosalvato1-ctrl wants to merge 1 commit into
codeaashu:mainfrom
mirkosalvato1-ctrl:oslifeguard/ci_bump-1168-1784789047

Conversation

@mirkosalvato1-ctrl

@mirkosalvato1-ctrl mirkosalvato1-ctrl commented Jul 23, 2026

Copy link
Copy Markdown

Proactive maintenance PR from OSS Lifeguard.

ci_bump:greetings.yml,JSONchecker.yml,issue-reminder.yml

Happy to adjust if maintainers prefer a different approach.

Fixes #1168

Summary by CodeRabbit

  • Chores
    • Updated automated repository workflows to use the latest checkout action version.
    • JSON validation, welcome messages, and scheduled issue reminders continue operating as before.

@bolt-new-by-stackblitz

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@vercel

vercel Bot commented Jul 23, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the icecream's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🎉 Incredible work, @mirkosalvato1-ctrl! 🚀

🔥 Welcome to DevDisplay — A space where developers and all the tech enthusiasts can connect, collaborate, code, create, and conquer in the tech ecosystem.

At DevDisplay, we don't just welcome contributors—we celebrate them! 🎊 Because here, your ideas matter. Your code matters. You matter. 🚀

💡 This isn't just about adding your profile. It's about making an impact, showcasing your skills, and standing out in the developer ecosystem.

Think of DevDisplay as your own project, not just another open-source contribution. We're not just a platform—we're a global movement redefining the tech space. Our vision is to be the go-to platform for developers and tech enthusiasts worldwide.

🚀 Innovation has no limits!
We encourage you to think beyond the ordinary. Got a revolutionary idea? Spot a gap in the tech world? DevDisplay can be the solution! We want contributors like you to dream big, build bold, and bring game-changing features to life.

🌍 DevDisplay is more than an open-source project. It's a global tech hub, a thriving community, and a platform where you can connect, collaborate, code, create, and conquer.

🔥 Keep pushing boundaries—we're just getting started!
If you put your 💯 into creating something exceptional, you could even join our Global Core Team and also you can lead DevDisplay as a Community Leader in your area, college, or university.


💡 Your issue is now in review!

  • Our maintainers will soon review your PR and provide feedback/suggestions. 🚀 Stay tuned, stay engaged, and get ready to bring your ideas to life! 💡

---

📢 Have ideas to improve DevDisplay? Let us know! We're always looking for innovative minds to shape the future of tech.

💬 Join the conversation. Grow with the community. You belong here. 🙌


📢 Join Our Global Developer Communities & Connect with Innovators:

📩 Need Help? Reach Out to the Team:

💻 Follow DevDisplay on Social Media & Stay Updated:

🔥 🌟 Thank You for Being Here!

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Three GitHub Actions workflows update their repository checkout steps to actions/checkout@v4; all other workflow behavior remains unchanged.

Changes

GitHub Actions checkout updates

Layer / File(s) Summary
Upgrade workflow checkout actions
.github/workflows/JSONchecker.yml, .github/workflows/greetings.yml, .github/workflows/issue-reminder.yml
The JSON checker, greeting, and issue reminder workflows now use actions/checkout@v4 instead of their previous checkout versions.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (3 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description omits most required template sections and gives only a brief maintenance note with a file list. Add the Description, Related Issues, Changes Proposed, Checklist, Screenshots, and Note to reviewers sections, and summarize the workflow updates in detail.
Linked Issues check ⚠️ Warning The PR only updates checkout actions in CI workflows and does not implement the idea submission and voting system from #1168. Implement the feature set from #1168, or relink the PR to the maintenance issue it actually addresses.
Out of Scope Changes check ⚠️ Warning The workflow version bumps are unrelated to the linked feature request and look like a separate maintenance change. Split the CI bump into its own PR and keep this one focused on the linked feature work.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title is concise and matches the CI workflow bump in the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Checkov (3.3.8)
.github/workflows/JSONchecker.yml

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'

.github/workflows/greetings.yml

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'

.github/workflows/issue-reminder.yml

Traceback (most recent call last):
File "/usr/local/bin/checkov", line 2, in
from checkov.main import Checkov
ModuleNotFoundError: No module named 'checkov'


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/JSONchecker.yml:
- Line 13: Disable persisted checkout credentials for every listed checkout step
by setting persist-credentials to false in .github/workflows/JSONchecker.yml
lines 13-13, .github/workflows/greetings.yml lines 16-16, and
.github/workflows/issue-reminder.yml lines 11-11; no job explicitly requires
authenticated Git operations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0abeb75b-b1f4-42a5-88a0-0416a32549e2

📥 Commits

Reviewing files that changed from the base of the PR and between e1ce099 and 71bf89c.

📒 Files selected for processing (3)
  • .github/workflows/JSONchecker.yml
  • .github/workflows/greetings.yml
  • .github/workflows/issue-reminder.yml

runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/checkout@v4

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow checkout usage =="
rg -n "actions/checkout|persist-credentials|persist_credentials|git " .github/workflows || true

echo "== relevant workflow excerpts =="
for f in .github/workflows/JSONchecker.yml .github/workflows/greetings.yml .github/workflows/issue-reminder.yml; do
  if [ -f "$f" ]; then
    echo "-- $f --"
    nl -ba "$f" | sed -n '1,140p'
  else
    echo "missing: $f"
  fi
done

echo "== local commit check for YAML syntax =="
python3 - <<'PY'
import glob, re
for path in sorted(glob.glob(".github/workflows/*.yml")):
    text = open(path, encoding="utf-8").read()
    print(f"{path}: lines={text.count(chr(10))+1}, checkout_count={text.count('actions/checkout')}, persist_count={text.count('persist-credentials')+text.count('persist_credentials')}")
PY

Repository: codeaashu/DevDisplay

Length of output: 516


🌐 Web query:

actions/checkout v4 persist-credentials defaults GitHub token local git configuration

💡 Result:

In actions/checkout@v4, the persist-credentials input defaults to true [1][2][3]. When set to true (default), the action configures the GITHUB_TOKEN (or the provided personal access token/SSH key) in the local git configuration [2][4]. Specifically, it writes an http.{url}.extraheader setting containing an authorization header directly into the local .git/config file [4][5]. This persistence allows subsequent steps in the same workflow job to perform authenticated git commands (such as pushing commits or fetching submodules) without needing to manually re-authenticate [2][5]. When persist-credentials is set to false, the action skips this configuration, which prevents these credentials from being written to the .git/config file [4][5]. This is often recommended as a security best practice to minimize the risk of credential leakage (e.g., if the repository workspace, including the .git directory, is accidentally uploaded as a job artifact) [6][5]. Note that if persist-credentials is left at its default of true, the persisted git configuration can take precedence over other authentication methods, such as gh auth setup-git [4]. If you do not require subsequent steps to have authenticated git access, setting persist-credentials: false is the recommended approach to opt out [2][4][5].

Citations:


Disable persisted checkout credentials across all workflows.

actions/checkout@v4 persists the GitHub token in local Git config by default. Set persist-credentials: false at each checkout unless the job explicitly needs authenticated Git operations:

  • .github/workflows/JSONchecker.yml#L13-L13
  • .github/workflows/greetings.yml#L16-L16
  • .github/workflows/issue-reminder.yml#L11-L11
🧰 Tools
🪛 zizmor (1.26.1)

[warning] 13-13: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)

📍 Affects 3 files
  • .github/workflows/JSONchecker.yml#L13-L13 (this comment)
  • .github/workflows/greetings.yml#L16-L16
  • .github/workflows/issue-reminder.yml#L11-L11
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/JSONchecker.yml at line 13, Disable persisted checkout
credentials for every listed checkout step by setting persist-credentials to
false in .github/workflows/JSONchecker.yml lines 13-13,
.github/workflows/greetings.yml lines 16-16, and
.github/workflows/issue-reminder.yml lines 11-11; no job explicitly requires
authenticated Git operations.

Source: Linters/SAST tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Project Idea Submission & Voting System 💌

1 participant