Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[scanner] deploy-gh-pages.yml: fetch full git history so the generated changelog renders entries

Closed Beginner friendly
  • Is something wrong?
#1,409 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #1484 by @mrbobbytables — merged

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
70/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
git, github-actions, javascript, yaml
Domain
ci-cd, devops

Research direction

Open .github/workflows/deploy-gh-pages.yml and find the checkout step in the build job. Add fetch-depth: 0 beside persist-credentials: false, then run npm run _build locally to confirm docs/community/changelog.md lists entries instead of the shallow-checkout fallback. Done when the deploy build renders the changelog. Workflow file edits may need a maintainer's review or permission.

Written by the indexing model from the issue text.

Description

agent/scanner blocked ci hive/hosted-available-lke648397-260827-5n31

Finding

The public changelog added for #1408 (ADR 0003, scripts/generate-changelog.mjs, wired into npm run _build) renders docs/community/changelog.md from git log --first-parent. The Deploy to GitHub Pages job checks out with the default fetch-depth: 1, so the deploy build has exactly one commit of history. The generator detects the shallow checkout and renders a fallback page that links GitHub's live merged-PR and commit views — accurate and zero-maintenance, but the site never shows the generated entries itself.

Recommendation

In .github/workflows/deploy-gh-pages.yml, change the build job's checkout step from:

      - name: Checkout
        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
        with:
          persist-credentials: false

to:

      - name: Checkout
        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
        with:
          persist-credentials: false
          fetch-depth: 0

That is the entire change; generate-changelog.mjs already handles both shapes of checkout, so no script or test changes are needed, and local/CI PR builds are unaffected either way.

Why this is an issue and not part of the PR

The PR that ships the changelog mechanism cannot contain this edit: the hive agent tier that opens hold-gated PRs has no Workflows permission, and GitHub rejects any push whose diff touches .github/workflows/**. This needs a human (or an agent tier carrying the Workflows permission) to land. Until then the deployed changelog page is the fallback, which is correct but thinner than the mechanism is built to produce.

Filed by scanner agent (ACMM L5 — hold-gated mode)

🐝 Hive Agent: scanner | Instance: hosted-available-lke648397-260827-5n31 | SHA: unknown

— hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.88

Dominant language
JavaScript
Stars
0
Forks
2
Avg merge
16h 38m
Merged PRs (30d)
608

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cncf/endusers

All issues in cncf/endusers

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.