Integrate Options.issueNumber Logic #103
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![fine-ai[bot]](https://avatars.githubusercontent.com/in/293841?s=60&v=4){kind=small}
added 2 commits
December 28, 2024 13:00
- Updated `action.yml` in `MishaKav/jest-coverage-comment` to include `issue-number` configurations from `MishaKav/pytest-coverage-comment`, maintaining the original context and purpose. - Transferred logic related to `issue-number` from `src/index.js` in `pytest-coverage-comment` to `src/index.ts` in `jest-coverage-comment`, adapting the code to TypeScript syntax and aligning with the existing code structure. - Enhanced `README.md` in `jest-coverage-comment` with documentation and examples for `issue-number`, ensuring relevance to the Jest coverage context. This update ensures consistency across repositories and extends the functionality of `issue-number` to the Jest coverage comment action.
- Updated `action.yml` to include an optional `issue-number` input with a clear and concise description. - Modified `src/index.ts` to retrieve the `issue-number` input using `core.getInput` and store it in a variable. Updated the `options` object to include the `issueNumber` property, parsing it as an integer if provided. - Enhanced `src/create-comment.ts` to utilize the `issueNumber` from the `options` object when creating or updating comments, modifying the API call to include the `issue_number` parameter. - Updated `README.md` to document the new `issue-number` input, explaining its purpose and providing an example of its usage in a GitHub Actions workflow.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for optional
issue-numberinput in GitHub Actionaction.ymlto include an optionalissue-numberinput with a clear and concise description.src/index.tsto retrieve theissue-numberinput usingcore.getInputand store it in a variable. Updated theoptionsobject to include theissueNumberproperty, parsing it as an integer if provided.src/create-comment.tsto utilize theissueNumberfrom theoptionsobject when creating or updating comments, modifying the API call to include theissue_numberparameter.README.mdto document the newissue-numberinput, explaining its purpose and providing an example of its usage in a GitHub Actions workflow.