Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ReversingLabs Workflow (Don't Merge) #782

Open
wants to merge 34 commits into
base: main
Choose a base branch
from

Conversation

developerkunal
Copy link

By submitting a PR to this repository, you agree to the terms within the Auth0 Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.

Description

Describe the purpose of this PR along with any background information and the impacts of the proposed change. For the benefit of the community, please do not assume prior context.

Provide details that support your chosen implementation, including: breaking changes, alternatives considered, changes to the API, etc.

If the UI is being changed, please provide screenshots.

References

Include any links supporting this change such as a:

  • GitHub Issue/PR number addressed or fixed
  • Auth0 Community post
  • StackOverflow post
  • Support forum thread
  • Related pull requests/issues from other repos

If there are no references, simply delete this section.

Testing

Describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.

Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.

Also include details of the environment this PR was developed in (language/platform/browser version).

  • This change adds test coverage for new/changed/fixed functionality

Checklist

  • I have added documentation for new/changed functionality in this PR or in auth0.com/docs
  • All active GitHub checks for tests, formatting, and security are passing
  • The correct base branch is being used, if not the default branch

Copy link

github-actions bot commented Jul 2, 2024

/hold

2 similar comments
Copy link

github-actions bot commented Jul 2, 2024

/hold

Copy link

github-actions bot commented Jul 2, 2024

/hold

Copy link

github-actions bot commented Jul 2, 2024

/hold

1 similar comment
Copy link

github-actions bot commented Jul 2, 2024

/hold

@developerkunal developerkunal marked this pull request as ready for review October 21, 2024 11:16
@developerkunal developerkunal requested a review from a team as a code owner October 21, 2024 11:16
tusharpandey13
tusharpandey13 previously approved these changes Oct 21, 2024
developerkunal and others added 8 commits October 23, 2024 21:40
By submitting a PR to this repository, you agree to the terms within the
[Auth0 Code of
Conduct](https://github.com/auth0/open-source-template/blob/master/CODE-OF-CONDUCT.md).
Please see the [contributing
guidelines](https://github.com/auth0/.github/blob/master/CONTRIBUTING.md)
for how to create and submit a high-quality PR for this repo.

### Description

> Describe the purpose of this PR along with any background information
and the impacts of the proposed change. For the benefit of the
community, please do not assume prior context.
>
> Provide details that support your chosen implementation, including:
breaking changes, alternatives considered, changes to the API, etc.
>
> If the UI is being changed, please provide screenshots.


### References

> Include any links supporting this change such as a:
>
> - GitHub Issue/PR number addressed or fixed
> - Auth0 Community post
> - StackOverflow post
> - Support forum thread
> - Related pull requests/issues from other repos
>
> If there are no references, simply delete this section.

### Testing

> Describe how this can be tested by reviewers. Be specific about
anything not tested and reasons why. If this library has unit and/or
integration testing, tests should be added for new functionality and
existing tests should complete without errors.
>
> Please include any manual steps for testing end-to-end or
functionality not covered by unit/integration tests.
>
> Also include details of the environment this PR was developed in
(language/platform/browser version).

- [ ] This change adds test coverage for new/changed/fixed functionality

### Checklist

- [ ] I have added documentation for new/changed functionality in this
PR or in auth0.com/docs
- [ ] All active GitHub checks for tests, formatting, and security are
passing
- [ ] The correct base branch is being used, if not the default branch
--artifact "${{ inputs.artifact-path }}" \
--name "${{ github.event.repository.name }}" \
--version "${{ inputs.version }}" \
--repository "${{ inputs.repository }}" \

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than requiring this to be passed in via a param, would it make sense just to use the default Actions var GITHUB_REPOSITORY ?

assuming this is a local action, so effectively it will only ever be publishing for auth0-react.

- name: Install Python dependencies
shell: bash
run: |
pip install --upgrade pip

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should not be necessary, considering you just ran the install with the Python actions. You'll see your workflow also indicates,

Requirement already satisfied: pip in /opt/hostedtoolcache/Python/3.10.15/x64/lib/python3.10/site-packages (24.2)

So I'd suggest to remove this.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure! will remove this.

rl-scanner:
uses: ./.github/workflows/rl-secure.yml
with:
node-version: 18

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dont think the scanner uses Node at all, does it? doesn't look like that action needs to do any building of the React SDK at all, just points the scanner to the artifact?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we are just passing node-version for npm build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants