Skip to content

Conversation

@jsji
Copy link
Contributor

@jsji jsji commented Nov 4, 2025

These workflow from upstream are not used at all, leaving them here might cause addition maintenance efforts, especially may post security concerns. Remove them.

@jsji jsji requested a review from a team as a code owner November 4, 2025 17:48
@jsji jsji temporarily deployed to WindowsCILock November 4, 2025 17:48 — with GitHub Actions Inactive
@jsji jsji self-assigned this Nov 4, 2025
Copy link
Contributor

@sarnex sarnex left a comment

Choose a reason for hiding this comment

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

overall idea is fine with me delta andrei's comments

@lukaszstolarczuk
Copy link
Contributor

nit: If you're removing the whole .ci dir, you could also clean it up from .github/CODEOWNERS (line: .ci/ @intel/dpcpp-devops-reviewers)

@jsji
Copy link
Contributor Author

jsji commented Nov 4, 2025

nit: If you're removing the whole .ci dir, you could also clean it up from .github/CODEOWNERS (line: .ci/ @intel/dpcpp-devops-reviewers)

Thanks, but I think we can leave it there just in case some files are being merged due to bad conflict resolutions.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2025

@intel/llvm-gatekeepers please consider merging

@sarnex sarnex merged commit ffde618 into intel:sycl Nov 4, 2025
28 checks passed
@KornevNikita
Copy link
Contributor

BTW scorecard.yml was also kind of used in this repo. It was reporting vulnerabilities. @intel/dpcpp-devops-reviewers should it be restored?

@jsji
Copy link
Contributor Author

jsji commented Nov 7, 2025

BTW scorecard.yml was also kind of used in this repo. It was reporting vulnerabilities. @intel/dpcpp-devops-reviewers should it be restored?

#20586

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.

5 participants