exuanbo / actions-deploy-gist Goto Github PK

Is it possible to upload multiple files to a gist using a glob pattern?

Something like this?

- uses: actions/checkout@v2
- name: Deploy
  uses: exuanbo/actions-deploy-gist@v1
  with:
    token: ${{ secrets.TOKEN }}
    gist_id: from_your_gist_url
    gist_description: "foos and bars"
    folder_path: ./dist/
    file_path:
    - foo.txt   # relative to folder_path = ./dist/foo.txt
    - bar/*.txt # relative to folder_path = ./dist/bar/*.txt

config:

      - name: XXXX
        uses: exuanbo/actions-deploy-gist@v1
        with:
          token: ${{ secrets.XXXX }}
          gist_id: XXXX
          gist_description: "XXXX"
          gist_file_name: XXXXX
          file_path: XXXXX

Log:

Run exuanbo/actions-deploy-gist@v1
  with:
    token: ***
    gist_id: XXXX
    gist_description: XXXX
    gist_file_name: XXXX
    file_path: XXXX
    file_type: text
  env:
    REPO_NAME: XXXX
    suffix: XXX
::group::Dump inputs
Dump inputs
  [INFO] GistId: XXXX
  [INFO] GistDescription: XXXX
  [INFO] GistFileName: XXXX
  [INFO] FilePath: XXXX
  [INFO] FileType: text
  ::endgroup::
::group::Deploy to gist
Deploy to gist
  [INFO] Action failed with "Error: Invalid request.
  
  "fileName" is not a permitted key."
  ##[debug]Node Action run completed with exit code 1
  ##[debug]Finishing: Deploy coverage badge

Just trying to setup this action and i encounter

  [INFO] Action failed with "Error: Not Found"

Sadly i have no idea what is not found, which makes it a bit hard to debug, die gist? the file?
or is it on githubs side and it cant find the action (that would be out of your scope of course)

If this is part of your action, a more descript error would be awesome!

https://github.com/exuanbo/actions-deploy-gist#prep-work says that I have to create a public gist.

However, I'd like to deploy my private repository to a private gist.

Is this possible with this action?

Would it be possible to create a new gist, rather than update an existing one?

Something like this:

- uses: actions/checkout@v2
- name: Deploy
  id: create-gist
  uses: exuanbo/actions-deploy-gist@v1
  with:
    token: ${{ secrets.TOKEN }}
    # Omit gist_id to create a new gist
    gist_description: "foo bar"
    gist_file_name: foo.bar
    file_path: ./dist/foo.bar
- name: Generate URL
  # Use output `gist_id` to get the created gist
  run: echo "https://some.endpoint.io?gistId=${{steps.create-gist.outputs.gist_id}}.json"

I am using this action to deploy a server-side built PDF to a gist. For some reason, the PDF deposited in the gist is different from the PDF that was built on the github server. The deposited PDF is about twice as large and corrupt. I have narrowed down the problem to the actual file transfer. Is it possible that this action is limited to ASCII files?

I get the following warning in the Actions tab:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: exuanbo/actions-deploy-gist@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Please add description parameter.

Ref: https://docs.github.com/en/rest/reference/gists#update-a-gist

Thank you for your great work.

Especially if this Action is executed daily, the gist's commit log will be huge. (example)

For this reason, I would like an option to squash all commits into one like: git reset $(git commit-tree 'HEAD^{tree}' -m "squashed")