Skip to content

Conversation

@twoGiants
Copy link

Changes

  • 🎁 tba ...
  • 🧹 tba ...

/kind enhancement

Fixes #tba...

Release Note


Docs


@knative-prow
Copy link

knative-prow bot commented Oct 22, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@knative-prow knative-prow bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/enhancement labels Oct 22, 2025
@knative-prow
Copy link

knative-prow bot commented Oct 22, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: twoGiants
Once this PR has been reviewed and has the lgtm label, please assign lkingland for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot requested review from jrangelramos and nainaz October 22, 2025 12:26
@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 22, 2025
@knative-prow knative-prow bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Oct 22, 2025
@twoGiants twoGiants force-pushed the issue-744-generate-github-actions-workflow branch 2 times, most recently from edad0e7 to 2b2cc43 Compare October 24, 2025 16:48
@knative-prow knative-prow bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Oct 24, 2025
Issue SRVOCF-744

Signed-off-by: Stanislav Jakuschevskij <[email protected]>
Issue SRVOCF-744

Signed-off-by: Stanislav Jakuschevskij <[email protected]>
Add 'func config ci' command as foundation for GitHub Actions
workflow generation. Extract function loader/saver interfaces
into cmd/common package and create cmd/testing factory for
reusable test helpers.

Issue SRVOCF-744

Signed-off-by: Stanislav Jakuschevskij <[email protected]>
Signed-off-by: Stanislav Jakuschevskij <[email protected]>
Add functionality to create GitHub Actions workflow directory and file
when running config ci command. Includes CIConfig struct for managing
workflow paths and permissions, with comprehensive test coverage.

Also fixes typo and refactors config tests to use helper functions.

Issue SRVOCF-744

Signed-off-by: Stanislav Jakuschevskij <[email protected]>
Signed-off-by: Stanislav Jakuschevskij <[email protected]>
- Add YAML structure types for workflow generation
- Generate hard coded remote-build-and-deploy workflow with checkout,
  func cli setup, and deploy steps
- Validate workflow structure and content in tests
- Export NewCIConfig for external use

Issue SRVOCF-744

Signed-off-by: Stanislav Jakuschevskij <[email protected]>
- Move CIConfig and workflow structs to cmd/ci package
- Separate config management (config.go) and workflow generation
  (workflow.go)
- Add CIConfig methods for path resolution
- Support custom workflow names via NewDefaultCIConfigWithName
- Update imports across cmd package

Issue SRVOCF-744

Signed-off-by: Stanislav Jakuschevskij <[email protected]>
- Add TDD and implementation guidelines to CLAUDE.md
- Create /creview slash command for code reviews
- Update issue-744 feature doc to mark Phase 2.1 complete

Issue SRVOCF-744

Signed-off-by: Stanislav Jakuschevskij <[email protected]>
Signed-off-by: Stanislav Jakuschevskij <[email protected]>
@twoGiants twoGiants force-pushed the issue-744-generate-github-actions-workflow branch from 48ac762 to c2000cd Compare November 7, 2025 12:16
@knative-prow-robot knative-prow-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 7, 2025
@codecov
Copy link

codecov bot commented Nov 7, 2025

Codecov Report

❌ Patch coverage is 44.26230% with 68 lines in your changes missing coverage. Please review.
✅ Project coverage is 63.71%. Comparing base (8f447a8) to head (c2000cd).

Files with missing lines Patch % Lines
cmd/ci/workflow.go 0.00% 34 Missing ⚠️
cmd/ci/config.go 44.00% 14 Missing ⚠️
cmd/testing/factory.go 0.00% 12 Missing ⚠️
cmd/config_ci.go 84.61% 2 Missing and 2 partials ⚠️
cmd/config.go 50.00% 3 Missing ⚠️
cmd/config_volumes.go 66.66% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3128      +/-   ##
==========================================
+ Coverage   62.85%   63.71%   +0.85%     
==========================================
  Files         148      155       +7     
  Lines       13202    13308     +106     
==========================================
+ Hits         8298     8479     +181     
+ Misses       3941     3842      -99     
- Partials      963      987      +24     
Flag Coverage Δ
e2e-tests 42.87% <36.36%> (+1.39%) ⬆️
integration-tests 58.13% <33.60%> (+1.56%) ⬆️
unit-tests 50.08% <33.60%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/enhancement size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants