Skip to content

Conversation

@rich7420
Copy link
Contributor

What changes were proposed in this pull request?

This pull request fixes an issue in the Update .asf.yaml step of the GitHub Actions workflow (.github/workflows/website.yml). Previously, the echo 'publish:' > .asf.yaml command overwrote the entire .asf.yaml file, causing the staging section to be lost. The updated file now matches the expected structure:

staging:
  profile: ~
  whoami: asf-site

publish:
  whoami: asf-site

How was this patch tested?

This patch was tested locally using the act tool to simulate the GitHub Actions workflow:

  • Run act -j build-website-deploy --container-architecture linux/amd64 to execute the workflow.
    Verified that the .asf.yaml file was correctly generated in the asf-site branch with both staging and publish sections.
  • Confirmed that the workflow steps (Checkout, Use Node.js, Install Yarn, Build Main Document, and Update .asf.yaml) completed successfully without errors.
  • or making a pr for trying online GitHub Actions workflow

Please review Ambari Contributing Guide before opening a pull request.

@jojochuang
Copy link
Contributor

So that problem is solved but there's still one more:

remote: Permission to apache/ambari-website.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/apache/ambari-website/': The requested URL returned error: 403

@rich7420
Copy link
Contributor Author

So that problem is solved but there's still one more:

remote: Permission to apache/ambari-website.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/apache/ambari-website/': The requested URL returned error: 403

It see we need to set Actions > General workflow permission Read and write permission of github-actions[bot]. I don't have permission to set. Need your help.

@jojochuang
Copy link
Contributor

I actually don't have the access. Will ask Apache Infra to set up it. Meanwhile, let's merge this one.

@jojochuang jojochuang merged commit 8996334 into apache:main Apr 17, 2025
1 check failed
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.

2 participants