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

chore(otterdog): adding / updating file(s) due to blueprint default-security-policy #5

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

eclipse-otterdog[bot]
Copy link
Contributor

This PR has been created automatically by Otterdog due to the following blueprint: Ensures a default SECURITY.md file exists.

This will add a default security policy to the .github repository of the project. The created PR can be edited as needed to adjust to the project's needs.
If a repository defines a more specific SECURITY.md file it will take precedence over the one present in the .github repo.

Copy link
Contributor

@erikbosch erikbosch left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@SebastianSchildt SebastianSchildt left a comment

Choose a reason for hiding this comment

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

Looks ok, keeping the default for now. In case of emergency foundation should know who to hunt down.

@SebastianSchildt SebastianSchildt force-pushed the otterdog/blueprint/default-security-policy branch from 39523a0 to d0140f5 Compare December 16, 2024 16:11
@SebastianSchildt SebastianSchildt merged commit 1ff19c1 into main Dec 16, 2024
2 checks passed
@eclipse-otterdog eclipse-otterdog bot deleted the otterdog/blueprint/default-security-policy branch December 16, 2024 16:13
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.

None yet

2 participants