Skip to content

Add GitHub Actions workflow for greetings#1

Merged
wsollers merged 3 commits into
mainfrom
wsollers-patch-1
Nov 2, 2025
Merged

Add GitHub Actions workflow for greetings#1
wsollers merged 3 commits into
mainfrom
wsollers-patch-1

Conversation

@wsollers

@wsollers wsollers commented Nov 2, 2025

Copy link
Copy Markdown
Owner

No description provided.

@wsollers
wsollers requested a review from Copilot November 2, 2025 15:59
Comment thread .github/workflows/greetings.yml Fixed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds a GitHub Actions workflow that automatically greets first-time contributors when they open their first issue or pull request in the repository.

Key Changes:

  • Introduces an automated greeting workflow using GitHub Actions
  • Configures the workflow to trigger on pull requests and issues
  • Sets up placeholder greeting messages for first-time contributors

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +15 to +16
issue-message: "Message that will be displayed on users' first issue"
pr-message: "Message that will be displayed on users' first pull request"

Copilot AI Nov 2, 2025

Copy link

Choose a reason for hiding this comment

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

The greeting messages are placeholder text and should be replaced with actual welcoming messages that provide useful information to first-time contributors (e.g., links to contribution guidelines, code of conduct, or how to get help).

Suggested change
issue-message: "Message that will be displayed on users' first issue"
pr-message: "Message that will be displayed on users' first pull request"
issue-message: |
👋 Hi there! Thank you for opening your first issue in this repository.
Please make sure to review our [Contribution Guidelines](https://github.com/OWNER/REPO/blob/main/CONTRIBUTING.md) and [Code of Conduct](https://github.com/OWNER/REPO/blob/main/CODE_OF_CONDUCT.md).
If you have any questions, feel free to ask or check our [Discussions](https://github.com/OWNER/REPO/discussions) for help.
pr-message: |
🎉 Thank you for submitting your first pull request!
We appreciate your contribution. Please ensure you have read our [Contribution Guidelines](https://github.com/OWNER/REPO/blob/main/CONTRIBUTING.md) and [Code of Conduct](https://github.com/OWNER/REPO/blob/main/CODE_OF_CONDUCT.md).
If you need any assistance, don't hesitate to reach out or visit our [Discussions](https://github.com/OWNER/REPO/discussions).

Copilot uses AI. Check for mistakes.
@github-actions

github-actions Bot commented Nov 2, 2025

Copy link
Copy Markdown
Contributor

Unit Test Results

 9 files  ±0  36 suites  ±0   0s ⏱️ ±0s
 6 tests ±0   6 ✅ ±0  0 💤 ±0  0 ❌ ±0 
54 runs  ±0  54 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 0591c6b. ± Comparison against base commit 0157411.

♻️ This comment has been updated with latest results.

@github-actions

github-actions Bot commented Nov 2, 2025

Copy link
Copy Markdown
Contributor

🛡️ Comprehensive SAST Security Analysis

Comprehensive SAST Security Analysis Report

Analysis Date: Sun Nov 2 16:17:54 UTC 2025
Repository: wsollers/utf_strings
Commit: e17f3c8
Scan Intensity: comprehensive

Security Tools Summary

🛡️ Trivy (Vulnerability & Misconfiguration)

Summary Report


Report Summary

┌────────┬──────┬─────────────────┬─────────┐
│ Target │ Type │ Vulnerabilities │ Secrets │
├────────┼──────┼─────────────────┼─────────┤
│   -    │  -   │        -        │    -    │
└────────┴──────┴─────────────────┴─────────┘
Legend:
- '-': Not scanned
- '0': Clean (no security findings detected)

🏗️ Checkov (Infrastructure Security)

ℹ️ Scan completed - check artifacts for details

Report Summary

github_actions scan results:

Passed checks: 1065, Failed checks: 10, Skipped checks: 0

Check: CKV_GHA_7: "The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. "
	FAILED for resource: on(SAST Security Scanning)
	File: /.github/workflows/sast-scanning.yml:24-35

		24 |       scan_intensity:
		25 |         description: "SAST scanning intensity level"
		26 |         required: false
		27 |         default: "comprehensive"
		28 |         type: choice
		29 |         options:
		30 |           - basic
		31 |           - comprehensive
		32 |           - deep
		33 | 
		34 | jobs:
		35 |   # ============================================================================

Check: CKV_GHA_7: "The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. "
	FAILED for resource: on(Create Release)
	File: /.github/workflows/create-release.yml:10-21

		10 |       version:
		11 |         description: "Version number (e.g., 0.0.1)"
		12 |         required: true
		13 |         type: string
		14 |       create_tag:
		15 |         description: "Create git tag if it does not exist"
		16 |         required: true
		17 |         type: boolean
		18 |         default: true
		19 | 
		20 | permissions:
		21 |   contents: write

Check: CKV_GHA_7: "The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. "
	FAILED for resource: on(Release Validation)
	File: /.github/workflows/release-validation.yml:8-14

		8  |       release_tag:
		9  |         description: "Release tag to validate"
		10 |         required: true
		11 |         type: string
		12 | 
		13 | jobs:
		14 |   # ============================================================================

🔐 Gitleaks (Secret Detection)

Scan Status: ✅ Primary scan completed successfully

Secrets Found: 0
No secrets detected in repository history!

🔧 Cppcheck (Static Code Analysis)

Issues Found:

  • Errors: 0
  • Warnings: 0
  • Style Issues: 0

No static analysis issues found!

🔍 Semgrep (Security Pattern Analysis)

Security Findings: 0
No security issues detected!

Next Steps

  1. Review all findings in the GitHub Security tab
  2. Prioritize critical and high severity issues
  3. Download detailed reports from workflow artifacts
  4. Implement fixes and re-run security scans
  5. Consider adjusting scan intensity for different scenarios
🔍 View scan configuration

Tools Used:

  • Trivy: Vulnerability and misconfiguration scanning
  • Checkov: Infrastructure security analysis
  • Gitleaks: Secret detection in git history
  • Cppcheck: Static code analysis for C/C++
  • Semgrep: Security pattern matching and code analysis

SARIF Results: All findings are automatically uploaded to the Security/Code Scanning tab for detailed analysis and tracking.

Scan Intensity: comprehensive

Workflow Run: View Details

@github-actions

github-actions Bot commented Nov 2, 2025

Copy link
Copy Markdown
Contributor

🛡️ Comprehensive SAST Security Analysis

Comprehensive SAST Security Analysis Report

Analysis Date: Sun Nov 2 16:26:14 UTC 2025
Repository: wsollers/utf_strings
Commit: e047bf2
Scan Intensity: comprehensive

Security Tools Summary

🛡️ Trivy (Vulnerability & Misconfiguration)

Summary Report


Report Summary

┌────────┬──────┬─────────────────┬─────────┐
│ Target │ Type │ Vulnerabilities │ Secrets │
├────────┼──────┼─────────────────┼─────────┤
│   -    │  -   │        -        │    -    │
└────────┴──────┴─────────────────┴─────────┘
Legend:
- '-': Not scanned
- '0': Clean (no security findings detected)

🏗️ Checkov (Infrastructure Security)

ℹ️ Scan completed - check artifacts for details

Report Summary

github_actions scan results:

Passed checks: 1071, Failed checks: 9, Skipped checks: 0

Check: CKV_GHA_7: "The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. "
	FAILED for resource: on(SAST Security Scanning)
	File: /.github/workflows/sast-scanning.yml:24-35

		24 |       scan_intensity:
		25 |         description: "SAST scanning intensity level"
		26 |         required: false
		27 |         default: "comprehensive"
		28 |         type: choice
		29 |         options:
		30 |           - basic
		31 |           - comprehensive
		32 |           - deep
		33 | 
		34 | jobs:
		35 |   # ============================================================================

Check: CKV_GHA_7: "The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. "
	FAILED for resource: on(Create Release)
	File: /.github/workflows/create-release.yml:10-21

		10 |       version:
		11 |         description: "Version number (e.g., 0.0.1)"
		12 |         required: true
		13 |         type: string
		14 |       create_tag:
		15 |         description: "Create git tag if it does not exist"
		16 |         required: true
		17 |         type: boolean
		18 |         default: true
		19 | 
		20 | permissions:
		21 |   contents: write

Check: CKV_GHA_7: "The build output cannot be affected by user parameters other than the build entry point and the top-level source location. GitHub Actions workflow_dispatch inputs MUST be empty. "
	FAILED for resource: on(Release Validation)
	File: /.github/workflows/release-validation.yml:8-14

		8  |       release_tag:
		9  |         description: "Release tag to validate"
		10 |         required: true
		11 |         type: string
		12 | 
		13 | jobs:
		14 |   # ============================================================================

🔐 Gitleaks (Secret Detection)

Scan Status: ✅ Primary scan completed successfully

Secrets Found: 0
No secrets detected in repository history!

🔧 Cppcheck (Static Code Analysis)

Issues Found:

  • Errors: 0
  • Warnings: 0
  • Style Issues: 0

No static analysis issues found!

🔍 Semgrep (Security Pattern Analysis)

Security Findings: 0
No security issues detected!

Next Steps

  1. Review all findings in the GitHub Security tab
  2. Prioritize critical and high severity issues
  3. Download detailed reports from workflow artifacts
  4. Implement fixes and re-run security scans
  5. Consider adjusting scan intensity for different scenarios
🔍 View scan configuration

Tools Used:

  • Trivy: Vulnerability and misconfiguration scanning
  • Checkov: Infrastructure security analysis
  • Gitleaks: Secret detection in git history
  • Cppcheck: Static code analysis for C/C++
  • Semgrep: Security pattern matching and code analysis

SARIF Results: All findings are automatically uploaded to the Security/Code Scanning tab for detailed analysis and tracking.

Scan Intensity: comprehensive

Workflow Run: View Details

@wsollers

wsollers commented Nov 2, 2025

Copy link
Copy Markdown
Owner Author

Need to fix those checkov issues eventually

@wsollers
wsollers merged commit 1611b39 into main Nov 2, 2025
24 checks passed
@wsollers
wsollers deleted the wsollers-patch-1 branch November 2, 2025 16:28
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