actions / actions/toolkit

@actions/core Provide way to get pull request opener in the Context.

Open
#695 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
5.9k
Forks
1.8k
PR merge metrics
No merged PRs in 30d

Description

Thank you 🙇‍♀ for wanting to create an issue in this repository. Before you do, please ensure you are filing the issue in the right place. Issues should only be opened on if the issue relates to code in this repository.

If your issue is relevant to this repository, please include the information below:

Describe the enhancement
A clear and concise description of what the features or enhancement you need.
I would like this for easier porting of ruby code to js to support Windows and OSX and drop docker unless you guys plan to enable use of ruby on OSX and Windows by using an action to set it up first so that way said actions can be executed properly.

Code Snippet
If applicable, add a code snippet to show the api enhancement.
Not sure how it would work, however I would like this added to the body of the Context.

Additional information
Add any other context about the feature here.
Take a look at this example ruby code, I would like to port this to JS to support Windows and OSX as well: https://github.com/Elskom/merge-dependabot/blob/main/entrypoint.sh

Contributor guide

Open the contributing guide

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.

Research direction

Start by reading the @actions/core Context API and compare the requested pull-request opener with the linked merge-dependabot entrypoint.sh example. Clarify how the opener should be exposed and what context data is available before deciding the API shape. Done means callers can reliably access the pull request opener in supported environments.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.