Skip to content

Add backend vulnerability scan task configuration#28

Merged
Mujhtech merged 1 commit into
mainfrom
chore/update-dagryn-workflow-govuln-2
Apr 22, 2026
Merged

Add backend vulnerability scan task configuration#28
Mujhtech merged 1 commit into
mainfrom
chore/update-dagryn-workflow-govuln-2

Conversation

@Mujhtech

Copy link
Copy Markdown
Owner

Description

[Provide a brief description of the changes in this pull request]

Related Issue

[If applicable, link to the issue this PR addresses]

Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Code refactor
  • Other (please specify)

Checklist

  • I have read the contribution guidelines
  • My code follows the project's coding style
  • I have tested my changes
  • I have updated the documentation accordingly

Additional Notes

[Add any additional information or context about the PR here]

Copilot AI review requested due to automatic review settings April 22, 2026 10:51
@dagryn-dev

dagryn-dev Bot commented Apr 22, 2026

Copy link
Copy Markdown

🟡 Dagryn workflow RUNNING

  • PR: Add backend vulnerability scan task configuration
  • Commit: Add backend vulnerability scan task configuration
  • Branch: chore/update-dagryn-workflow-govuln-2
  • SHA: 300975b

View run in Dagryn

@dagryn-dev

dagryn-dev Bot commented Apr 22, 2026

Copy link
Copy Markdown

🟡 Dagryn workflow RUNNING

  • PR: Add backend vulnerability scan task configuration
  • Commit: Add backend vulnerability scan task configuration
  • Branch: chore/update-dagryn-workflow-govuln-2
  • SHA: 300975b

View run in Dagryn

@dagryn-dev

dagryn-dev Bot commented Apr 22, 2026

Copy link
Copy Markdown

🟡 Dagryn workflow RUNNING

  • PR: Add backend vulnerability scan task configuration
  • Commit: Add backend vulnerability scan task configuration
  • Branch: chore/update-dagryn-workflow-govuln-2
  • SHA: 300975b

View run in Dagryn

@dagryn-dev

dagryn-dev Bot commented Apr 22, 2026

Copy link
Copy Markdown

🟡 Dagryn workflow RUNNING

  • PR: Add backend vulnerability scan task configuration
  • Commit: Add backend vulnerability scan task configuration
  • Branch: chore/update-dagryn-workflow-govuln-2
  • SHA: 300975b

View run in Dagryn

@Mujhtech
Mujhtech merged commit 6bf5101 into main Apr 22, 2026
3 of 6 checks passed
@dagryn-dev

dagryn-dev Bot commented Apr 22, 2026

Copy link
Copy Markdown

🟡 Dagryn workflow RUNNING

  • PR: Add backend vulnerability scan task configuration
  • Commit: Add backend vulnerability scan task configuration
  • Branch: chore/update-dagryn-workflow-govuln-2
  • SHA: 300975b

View run in Dagryn

@dagryn-dev

dagryn-dev Bot commented Apr 22, 2026

Copy link
Copy Markdown

🟡 Dagryn workflow RUNNING

  • PR: Add backend vulnerability scan task configuration
  • Commit: Add backend vulnerability scan task configuration
  • Branch: chore/update-dagryn-workflow-govuln-2
  • SHA: 300975b

View run in Dagryn

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

Adds missing Dagryn task configuration so the backend vulnerability scan runs in the correct Go module working directory (backend/), aligning it with the existing backend build/test/lint tasks and CI workflow configuration.

Changes:

  • Set workdir = "backend" for tasks.backend-vulnerability-scan in dagryn.toml.
Comments suppressed due to low confidence (1)

dagryn.toml:85

  • The vulnerability scan task runs govulncheck but writes/exports the report as gosec-report.json, which is misleading (gosec is a different tool). Consider renaming the report file (and outputs entry) to something like govulncheck-report.json to avoid confusion and accidental misinterpretation by consumers.
command = "govulncheck ./... -json > gosec-report.json"
uses = ["setup-go", "golang-vul"]
needs = ["backend-install", "backend-build"]
inputs = ["**/*.go", "go.mod", "go.sum"]
outputs = ["gosec-report.json"]

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

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.

2 participants