v1.1.0

What's Changed

This release introduces several enhancements to make the GitHub Script with Post action more configurable, flexible, and integration-friendly.

✨ New Features

• 🧩 Post Target Control — Added new input post-target
  You can now choose where results are posted:

  • github-step-summary — append output only to the workflow summary
  • pull-request — comment directly on the pull request
  • both (default) — post to both locations

  [View commit → df47b38](df47b38)

• 🔁 Pass-Through Inputs for actions/github-script
  The action now fully supports all upstream configuration options such as:

  • github-token
  • debug
  • user-agent
  • previews
  • result-encoding
  • retries
  • retry-exempt-status-codes
  • base-url
    This allows users to fine-tune GitHub API behavior directly.

  [View commit → db90677](db90677)

• 📤 Output Result Handling
  The result of your custom JavaScript is now automatically captured and exposed as an output named result.
  Downstream workflow steps can easily access it via:

  ${{ steps.<id>.outputs.result }}

  [View commit → a48ef4f](a48ef4f)

⚙️ Example Usage

- name: Run custom JavaScript and post results
  id: post
  uses: aguilita1/[email protected]
  with:
    post-target: pull-request
    script: |
      return "✅ Custom script executed successfully!";

You can then reference the result in later steps:

- name: Log result
  run: echo "Output: ${{ steps.post.outputs.result }}"

🧾 Summary

This update enhances flexibility, improves output handling, and makes the action fully compatible with upstream actions/github-script configuration options — paving the way for more advanced automation workflows.

---

Full Changelog: v1.0.0...v1.1.0