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

fix(ci): correct input type for allow-dependencies-licenses in Dependency Review GH action #28343

Merged
merged 1 commit into from May 6, 2024

Conversation

hainenber
Copy link
Contributor

@hainenber hainenber commented May 4, 2024

fix(ci): correct input type for allow-dependencies-licenses for Dependency Review GH action

SUMMARY

Some of my PRs got failed in the GH action due to incorrect input type for said GH action. This change is to restore the CI job's functionality.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before
image

After
image

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

Copy link
Member

@mistercrunch mistercrunch left a comment

Choose a reason for hiding this comment

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

Oooops my bad, thanks for fixing it!

@mistercrunch mistercrunch merged commit bf5ff55 into apache:master May 6, 2024
31 of 32 checks passed
@hainenber hainenber deleted the fix-dep-review-gh-action branch May 6, 2024 16:00
mistercrunch added a commit that referenced this pull request May 6, 2024
#28343 fixes an issue where I had broken a specific github action workflow in a previous PR without realizing I did. If/when altering the yaml, if the yaml itsefl is valid (we have a check for that) yet the schema is not - either through passing the right data structure or required types, the action just won't run and the PR is still mergeable. The failure gets somewhat burried on the Actions tab (at the bottom of https://github.com/apache/superset/actions)

Here I'm hoping that this pre-commit hook will both catch this early, and prevent the PR from being mergeable.

Find out more about the hook here: https://github.com/mpalmer/action-validator
@mistercrunch
Copy link
Member

Hoping #28358 will prevent similar troubles

# license: https://applitools.com/legal/open-source-terms-of-use/
# pkg:npm/[email protected]
# selecting BSD-3-Clause licensing terms for node-forge to ensure compatibility with Apache
allow-dependencies-licenses: pkg:npm/[email protected], pkg:npm/applitools/core, pkg:npm/applitools/core-base, pkg:npm/applitools/css-tree, pkg:npm/applitools/ec-client, pkg:npm/applitools/eg-socks5-proxy-server, pkg:npm/applitools/eyes, pkg:npm/applitools/eyes-cypress, pkg:npm/applitools/nml-client, pkg:npm/applitools/tunnel-client, pkg:npm/applitools/utils, pkg:npm/[email protected]
Copy link
Member

Choose a reason for hiding this comment

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

Any reason to switch from multiline to single line? This seems less readable and harder to review future changes if only one dependency changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The GH action only accepts the input arg as single line. Maybe it will get fixed in the future version but for now, it's the only way proceeding

imancrsrk pushed a commit to imancrsrk/superset that referenced this pull request May 10, 2024
jzhao62 pushed a commit to jzhao62/superset that referenced this pull request May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
github_actions Pull requests that update GitHub Actions code size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants