
Product
Introducing Pull Request Stories to Help Security Teams Track Supply Chain Risks
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.
siteleaf-updater
Advanced tools
update the index file of your project's siteleaf project with your repository's README.md file
update the index file of your project's siteleaf project with your repository's README.md file
When hosting GitHub Pages, there is a common discrepancy one faces when choosing the place to host their page files.
Hosting GitHub Pages the master branch has the advantage that files can be shared with the project (including the README). However, pages usually stand alone without a dependency to or from the project's files. Hence, there might be numerous commits that cause an avoidable overhead to merges, CI, and pulls.
Hosting the pages on a dedicated branch (e.g., gh-pages
) has the benefit that this beforementioned overhead is avoided.
Separate concerns are rooted in separate trees, just as it is supposed to be.
However, normally, developers only want to publish their README with a few additions.
There is no integrated way or known method in GitHub to sync the README file without hooks or different workarounds.
This circumstance impairs common maintenance and automation requirements.
index
by default).siteleaf-updater
for automated doc updates.Action Input | CLI Parameter | Environment Variable | Default | Description |
---|---|---|---|---|
api-key | api-key | SITELEAF_API_KEY | required | the API key that grants access to the repository's siteleaf project |
api-secret | api-secret | SITELEAF_API_SECRET | required | the API secret that grants access to the repository's siteleaf project |
site | site | SITELEAF_SITE | required | the id of the siteleaf site to be updated |
page | page | SITELEAF_PAGE | index | the target page of the siteleaf site to be updated |
file | file | SITELEAF_MD_SOURCE | README.md | the path to the local Markdown file to push |
publish | publish | - | false | allows publishing the site after its update |
steps:
- name: update site
uses: gofunky/siteleaf-updater@v2
with:
api-key: ${{ secrets.SITELEAF_KEY }}
api-secret: ${{ secrets.SITELEAF_SECRET }}
site: 'my-site'
page: 'contribution'
file: 'CONTRIBUTION.md'
publish: true
FAQs
update the index file of your project's siteleaf project with your repository's README.md file
The npm package siteleaf-updater receives a total of 11 weekly downloads. As such, siteleaf-updater popularity was classified as not popular.
We found that siteleaf-updater demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket’s new Pull Request Stories give security teams clear visibility into dependency risks and outcomes across scanned pull requests.
Research
/Security News
npm author Qix’s account was compromised, with malicious versions of popular packages like chalk-template, color-convert, and strip-ansi published.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.