Sitelet https://github.com/ElonCoding/ElonCoding/pull/2/files
Skip to content

Add GitHub Actions workflow for 3D Skyline generation #2

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.

Sign up for GitHub

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

Merged
ElonCoding merged 1 commit into from
Aug 6, 2026
Merged

Add GitHub Actions workflow for 3D Skyline generation #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
34 changes: 34 additions & 0 deletions .github/workflows/3d.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
name: Generate 3D Contribution Skyline

on:
schedule:
- cron: '0 0 * * *'
workflow_dispatch:

permissions:
contents: write

jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout repo
uses: actions/checkout@v3
Comment on lines +15 to +16

@coderabbitai coderabbitai Bot Aug 6, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The 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 -euo pipefail

echo "Files:"
git ls-files .github/workflows | sed -n '1,120p'

echo
echo "workflow 3d.yml context:"
cat -n .github/workflows/3d.yml

echo
echo "Search for push target and workflow_dispatch in workflows:"
rg -n "workflow_dispatch|push|ref:|actions/checkout|on:" .github/workflows -S

Repository: ElonCoding/ElonCoding

Length of output: 2135

🌐 Web query:

actions/checkout v3 ref input default pull_request branch event default branch

💡 Result:

For the actions/checkout action (including version v3), the ref input behaves according to the following logic: When checking out the repository that triggered the workflow, the ref input defaults to the reference or SHA associated with that event [1][2]. If it is not triggered by an event, or in cases where the reference is not automatically determined, it defaults to the repository's default branch [1][2]. Regarding the pull_request event specifically: By default, actions/checkout checks out a merge commit that represents the merge between the pull request branch and the base branch, rather than the pull request head commit itself [3][4]. Because this merge commit is a detached HEAD, users who specifically want to work with the branch head or a different reference must explicitly set the ref input, for example by using ${{ github.head_ref }} [5][6]. In the context of the pull_request_target event, the action defaults to the base repository's default branch for security reasons, as this event runs in a context that has access to secrets [3].

Citations:

🌐 Web query:

GitHub Actions workflow_dispatch inputs branch ref checkout default branch

💡 Result:

To use the workflow_dispatch trigger with custom inputs and handle branch references or default branch checkouts in GitHub Actions, observe the following requirements and behaviors. Workflow Trigger Requirements The workflow_dispatch event trigger only functions when the workflow file is present on the repository's default branch [1][2]. If you attempt to trigger it manually via the GitHub UI or API while the workflow file exists only on a non-default branch, the workflow will not be available to run [2][3]. Handling Branch References When you manually trigger a workflow via the GitHub UI, you can select the branch or tag to run against. When using the GitHub CLI (gh) or REST API, you must specify the branch/ref explicitly using the --ref flag or the ref request parameter [2]. Checkout Behavior The actions/checkout action is responsible for cloning your code into the runner [4]. Its behavior regarding the branch is as follows: - By default, if the ref input is omitted, actions/checkout checks out the reference (branch, tag, or SHA) that triggered the workflow [4][5]. - If you have manually triggered the workflow on a specific branch (e.g., feature-branch), actions/checkout will default to that branch [4]. - If you specifically require the default branch regardless of what triggered the workflow, you must explicitly set the ref input in your checkout step: - uses: actions/checkout@v7 with: ref: main # Replace 'main' with your actual default branch name Summary of Workflow Dispatch inputs - Inputs are defined in the workflow file under on.workflow_dispatch.inputs and are accessible within the workflow via the inputs context (or github.event.inputs) [1]. - These inputs are independent of the branch reference [1]. Whether you run the workflow on the default branch or a feature branch, the same set of inputs will be available to the workflow [1]. If you are using third-party actions like benc-uk/workflow-dispatch to trigger workflows across different repositories, you may need to explicitly pass the ref input to ensure the target workflow operates on the correct branch, especially if the target repository has a different default branch than the caller [6][7].

Citations:

Checkout main before pushing to main.

workflow_dispatch can run this workflow from a non-default branch. With no ref input, actions/checkout checks out the selected branch, but the final command still pushes that branch’s HEAD to main. Set the checkout ref explicitly so every run builds and commits from main.

Proposed fix 
       - name: Checkout repo
         uses: actions/checkout@v3
+        with:
+          ref: main
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Checkout repo
uses: actions/checkout@v3
- name: Checkout repo
uses: actions/checkout@v3
with:
ref: main
🧰 Tools
🪛 actionlint (1.7.12)

[error] 16-16: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 zizmor (1.29.0)

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

(artipacked)

🤖 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/3d.yml around lines 15 - 16, Update the Checkout repo step
using actions/checkout so it explicitly checks out the main ref, ensuring
workflow_dispatch runs build and commit from main regardless of the selected
branch.

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow file =="
if [ -f .github/workflows/3d.yml ]; then
  nl -ba .github/workflows/3d.yml | sed -n '1,120p'
else
  echo ".github/workflows/3d.yml not found"
fi

echo
echo "== github token usages in workflows =="
rg -n "GITHUB_TOKEN|set-url|git push|persist-credentials|actions/checkout|Platane/snk" .github/workflows || true

Repository: ElonCoding/ElonCoding

Length of output: 219

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow file =="
if [ -f .github/workflows/3d.yml ]; then
  awk '{printf "%6d\t%s\n", NR, $0}' .github/workflows/3d.yml | sed -n '1,120p'
else
  echo ".github/workflows/3d.yml not found"
fi

echo
echo "== github token usages in workflows =="
grep -nE "GITHUB_TOKEN|set-url|git push|persist-credentials|actions/checkout|Platane/snk" .github/workflows || true

Repository: ElonCoding/ElonCoding

Length of output: 1454

🌐 Web query:

actions/checkout persist-credentials default true local Git configuration persist-credentials false

💡 Result:

The persist-credentials input for the GitHub Actions checkout action (actions/checkout) determines whether the repository's authentication token or SSH key is configured in the local Git configuration [1][2]. The default value for persist-credentials is true [1][2]. When set to true (the default), the action configures the authentication credentials into the local Git configuration, which allows your workflow steps to run authenticated Git commands (such as git fetch or git push) automatically [1][3]. The action ensures these credentials are removed during the post-job cleanup process [1][4]. When you set persist-credentials to false, the action will not configure these credentials in the local Git configuration [1][2]. This is an optional setting used to opt-out of this behavior [1][5]. Note: While there have been discussions and community requests to change this default to false to further reduce the risk of credential exposure, the current authoritative configuration in the official actions/checkout repository maintains the default value as true [1][6][2]. Recent security improvements have been implemented to store these credentials in a separate file under $RUNNER_TEMP rather than directly in.git/config, while still allowing git commands to work seamlessly without requiring workflow changes [3][7].

Citations:

🌐 Web query:

Platane/snk v3 GitHub Action Docker entrypoint script source

💡 Result:

The Platane/snk v3 GitHub Action does not use a traditional entrypoint script file. Instead, the Docker container is configured to run a specific command directly [1]. As specified in the project's Dockerfile, the container uses the following instruction to execute the application: CMD ["bun", "/action-release/index.js"] The Docker container environment is built using Bun, and the entry point for the action's logic is the JavaScript file located at /action-release/index.js [1]. This file contains the bundled code generated during the project's build process [1]. Users do not need to interact with this entrypoint file directly, as it is managed automatically by the GitHub Action's Docker configuration [2][1].

Citations:

🌐 Web query:

Platane/snk v3 github.com/Dockerfile CMD bun /action-release/index.js action.yml Docker run uses Dockerfile

💡 Result:

Platane/snk is a popular GitHub Action that generates an animated snake game visualization based on a user's GitHub contribution graph [1][2]. The action supports both GIF and SVG output formats [1][3]. Regarding the specific components you mentioned: Dockerfile and CMD: The project uses a Dockerfile that leverages the bun runtime (specifically oven/bun) [4]. The final image is configured with the command CMD ["bun", "/action-release/index.js"], which executes the main action logic upon container startup [4]. action.yml: The action definition file (action.yml) specifies that the action runs using a docker container [5]. It points to a specific image reference (image: docker://platane/snk@sha256:...) to ensure a consistent, versioned execution environment [5]. Usage: Users can invoke this action in their GitHub workflow files using the syntax - uses: Platane/snk@v3 [1][6]. For users who only require SVG output and prefer a faster, non-Docker implementation, the project also provides a secondary action: uses: Platane/snk/svg-only@v3 [3][7].

Citations:

Limit GITHUB_TOKEN exposure to the final push.

actions/checkout persists the token in local Git credentials by default. The following Platane/snk@v3 Docker container step can access the checked-out workspace, and the commit/push step later also writes the token into the origin URL. Disable persisted credentials at checkout and authenticate only the final git push with a command-scoped http.extraheader header.

Proposed fix 
       - name: Checkout repo
         uses: actions/checkout@v3
         with:
+          persist-credentials: false
...
-          git remote set-url origin https://x-access-token:${TOKEN}`@github.com/`${{ github.repository }}.git
-          git push origin HEAD:main
+          git -c "http.extraheader=AUTHORIZATION: bearer ${TOKEN}" push origin HEAD:main
🧰 Tools
🪛 actionlint (1.7.12)

[error] 16-16: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 zizmor (1.29.0)

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

(artipacked)

🤖 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/3d.yml around lines 15 - 16, Update the checkout step
using actions/checkout@v3 to disable persisted credentials, then modify the
final git push command to authenticate only for that command via an
http.extraheader using GITHUB_TOKEN. Ensure the Platane/snk@v3 step cannot
access stored Git credentials while preserving the existing push behavior.

Source: Linters/SAST tools

@coderabbitai coderabbitai Bot Aug 6, 2026

Copy link
Copy Markdown

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:

#!/bin/bash
set -euo pipefail

gh api repos/actions/checkout/releases/latest --jq '.tag_name'
rg -n -C 2 'actions/checkout@|runs-on:' .github/workflows

Repository: ElonCoding/ElonCoding

Length of output: 984

🌐 Web query:

GitHub Hosted Runners Node.js Runtime Removed v12 v16 actions/checkout deprecation

💡 Result:

GitHub Actions has removed support for older Node.js runtimes as they reached their end-of-life (EOL). The removal of Node.js 12 and Node.js 16 followed established deprecation cycles, requiring users and action maintainers to upgrade their dependencies to newer, supported versions [1][2][3]. Summary of Node.js Runtime Deprecations in GitHub Actions: Node.js 12: Support was removed from GitHub Actions runners on August 14, 2023, following a deprecation process that began in 2022 [2][4][5]. Node.js 16: After reaching EOL, Node.js 16 was removed from GitHub Actions runners on November 12, 2024 [1][3]. Node.js 20: Following the EOL of Node.js 20 in April 2026, it was removed from GitHub runner images by May 2026, with defaults migrated to Node.js 22 [6]. Impact on actions/checkout: The actions/checkout action, like many other official actions, required updates to align with these runtime changes. When Node.js 12 and 16 were deprecated, older versions of actions/checkout (such as v2 or early v3 releases) that relied on these runtimes triggered deprecation warnings in user workflows [7][8]. To resolve these warnings and ensure continued functionality, users were required to update to newer versions of the action (e.g., updating to v3 or v4) that had been refactored to run on the then-current supported Node.js version [7]. Recommendation: To avoid issues with runtime deprecations, users should always use the latest major version of official actions, such as actions/checkout@v4. You can verify which runtime an action uses by checking its action.yml file in its respective GitHub repository [9]. It is recommended to follow the official GitHub Changelog to stay informed about upcoming deprecation timelines for runner runtimes [1][10].

Citations:

🌐 Web query:

actions/checkout v3 Node16 action.yml

💡 Result:

The actions/checkout@v3 action uses the Node.js 16 runtime [1][2]. GitHub transitioned away from Node.js 16 to Node.js 20 in GitHub Actions [3], leading to deprecation warnings for actions that rely on the older runtime, including actions/checkout@v3 [3][4][5]. While actions/checkout@v3 remains technically functional (and has received recent security-related backports in version v3.7.0) [6][7], it is recommended to upgrade to actions/checkout@v4 or later to use an action that runs on a supported Node.js version [3][4][5]. You can view the specific configuration for v3 in its official action.yml file on GitHub [8]. To address deprecation warnings, simply update your workflow configuration from: - uses: actions/checkout@v3 to: - uses: actions/checkout@v4 (or the latest available major version) [5].

Citations:

🌐 Web query:

GitHub hosted runners removal node16 ubuntu-latest November 12 2024

💡 Result:

GitHub announced that Node.js 16 would reach its end-of-life on the Actions runner on November 12, 2024 [1]. From this date forward, Node.js 16 was no longer included in the GitHub-hosted runners, and users were required to migrate their actions to Node.js 20 to avoid workflow disruption [1]. While the general end-of-life date for the runner was set for November 12, 2024 [1], the specific removal dates from various runner images varied slightly: - Ubuntu 24.04: Node.js 16 was removed on October 21, 2024 [2]. - Ubuntu 20.04 and 22.04: Node.js 16 was scheduled for removal on November 18, 2024 [3]. This transition was part of a larger deprecation process that began earlier in 2024 [4]. By late 2024, GitHub had completed the transition to Node.js 20 as the required runtime for GitHub Actions [1].

Citations:

Replace the unsupported checkout action.

actions/checkout@v3 depends on the Node16 action runner, which is no longer available on GitHub-hosted runners. Update .github/workflows/3d.yml to a supported release, such as actions/checkout@v4 or later, and pin it to a full commit SHA.

🧰 Tools
🪛 actionlint (1.7.12)

[error] 16-16: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🪛 zizmor (1.29.0)

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

(artipacked)

🤖 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/3d.yml at line 16, Update the checkout step using
actions/checkout in the 3D workflow to a supported release, such as v4 or later,
and pin the action to its complete commit SHA rather than a tag.

Source: Linters/SAST tools


- name: Generate Skyline
uses: Platane/snk@v3
with:
github_user_name: ElonCoding
outputs: |
output/profile-3d-contrib/profile-night-rainbow.svg

- name: Commit and Push SVG
env:
TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
git config --global user.name 'ElonCoding'
git config --global user.email 'sharmaparikshit405@gmail.com'
Comment on lines +29 to +30

@coderabbitai coderabbitai Bot Aug 6, 2026

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

Use a bot identity for generated commits.

The workflow records sharmaparikshit405@gmail.com as the author email in every generated commit. If this repository is public, the address becomes permanent public metadata. Use the GitHub Actions bot identity instead. GitHub documents the standard bot name and noreply address. (github.com)

Proposed fix 
-          git config --global user.name 'ElonCoding'
-          git config --global user.email 'sharmaparikshit405@gmail.com'
+          git config user.name 'github-actions[bot]'
+          git config user.email '41898282+github-actions[bot]`@users.noreply.github.com`'
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
git config --global user.name 'ElonCoding'
git config --global user.email 'sharmaparikshit405@gmail.com'
git config user.name 'github-actions[bot]'
git config user.email '41898282+github-actions[bot]`@users.noreply.github.com`'
🤖 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/3d.yml around lines 29 - 30, Update the git identity
configuration in the workflow’s generated-commit setup to use GitHub Actions’
standard bot name and noreply email instead of the personal name and address.
Keep the existing global git configuration behavior unchanged.

git add output || echo "Nothing to add"
git commit -m "🛰️ Update 3D Skyline graph" || echo "Nothing to commit"
Comment on lines +31 to +32

@coderabbitai coderabbitai Bot Aug 6, 2026

Copy link
Copy Markdown

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

Do not hide staging and commit failures.

|| echo masks every error, not only the no-change case. If staging or commit fails, git push can still return success without publishing a new SVG. Let real Git errors fail the step and check for staged changes explicitly.

Proposed fix 
-          git add output || echo "Nothing to add"
-          git commit -m "🛰️ Update 3D Skyline graph" || echo "Nothing to commit"
+          git add output
+          if git diff --cached --quiet; then
+            echo "Nothing to commit"
+            exit 0
+          fi
+          git commit -m "🛰️ Update 3D Skyline graph"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
git add output || echo "Nothing to add"
git commit -m "🛰️ Update 3D Skyline graph" || echo "Nothing to commit"
git add output
if git diff --cached --quiet; then
echo "Nothing to commit"
exit 0
fi
git commit -m "🛰️ Update 3D Skyline graph"
🤖 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/3d.yml around lines 31 - 32, Update the workflow step
containing git add, git commit, and git push so staging and commit failures
propagate instead of being masked by “|| echo”. Check explicitly whether changes
are staged before committing, allowing the no-change case without suppressing
real Git errors, and ensure the push only proceeds when the SVG update was
successfully staged and committed.

git remote set-url origin https://x-access-token:${TOKEN}@github.com/${{ github.repository }}.git
git push origin HEAD:main
Comment on lines +25 to +34

@coderabbitai coderabbitai Bot Aug 6, 2026

Copy link
Copy Markdown

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:

#!/bin/bash
set -euo pipefail

echo "== candidate file =="
if [ -f .github/workflows/3d.yml ]; then
  nl -ba .github/workflows/3d.yml | sed -n '1,80p'
else
  echo ".github/workflows/3d.yml not found"
fi

echo
echo "== all workflow files =="
git ls-files '.github/workflows/*' | sort

echo
echo "== concurrency declarations in workflows =="
rg -n "concurrency:|cancel-in-progress|schedule:|workflow_dispatch" .github/workflows || true

Repository: ElonCoding/ElonCoding

Length of output: 220

🏁 Script executed:

#!/bin/bash
set -u

echo "== candidate file =="
if [ -f .github/workflows/3d.yml ]; then
  awk '{printf "%6d  %s\n", NR, $0}' .github/workflows/3d.yml | sed -n '1,100p'
else
  echo ".github/workflows/3d.yml not found"
fi

echo
echo "== all workflow files =="
git ls-files '.github/workflows/*' | sort

echo
echo "== concurrency declarations in workflows =="
grep -RInE 'concurrency:|cancel-in-progress|schedule:|workflow_dispatch' .github/workflows || true

Repository: ElonCoding/ElonCoding

Length of output: 1713

Serialize skyline runs before pushing.

This workflow runs on both schedule and manual dispatch, but it has no workflow-level concurrency control. Concurrent runs can commit from the same base and make one git push origin HEAD:main fail. Add concurrency with group: generate-3d-skyline and cancel-in-progress: false.

🤖 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/3d.yml around lines 25 - 34, The workflow lacks
serialization for scheduled and manually dispatched skyline runs, allowing
concurrent pushes to conflict. Add workflow-level concurrency configuration
using group generate-3d-skyline and cancel-in-progress set to false, leaving the
Commit and Push SVG steps unchanged.