Add build automation with Makefile and update github workflows#18
Merged
Conversation
Signed-off-by: Alex Lovell-Troy <alex@lovelltroy.org>
- Added SPDX license headers to various source files, including Go files, README, and JSON files. - Updated generated files with new timestamps and license information. - Refactored integration tests to ensure proper cleanup of resources. - Improved error handling in the Redfish client. - Cleaned up unnecessary whitespace and comments in main server logic. - Updated the discovery snapshot types to include new validation rules. - Enhanced the device handlers and reconciler registration processes. Co-authored-by: Copilot <copilot@github.com> Signed-off-by: Alex Lovell-Troy <alex@lovelltroy.org>
- Regenerated OpenAPI and route files with updated project name and version. - Updated Go module dependencies to latest versions, including Fabrica and Cobra. - Refactored client code to support JWT bearer token for authorization. - Updated copyright year to 2026 across all generated files. - Removed unimplemented event bus types from event bus middleware. - Enhanced comments and documentation for clarity and consistency. Signed-off-by: Alex Lovell-Troy <alex@lovelltroy.org>
bmcdonald3
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces comprehensive improvements to project automation, developer tooling, and compliance for the
fru-trackerrepository. The changes add a newMakefilewith a wide range of developer commands, introduce several GitHub Actions workflows for CI/CD, code quality, security, and compliance, and establish project metadata and configuration for reproducible builds and code generation. These enhancements significantly improve the project's maintainability, automation, and adherence to best practices.Key changes:
Developer Tooling and Automation
Makefilewith targets for building, testing (including integration and coverage), linting, formatting, vulnerability scanning, code generation, Docker operations, REUSE compliance, pre-commit hooks, and local GitHub Actions workflow testing. This provides a unified developer experience and enforces project standards.Continuous Integration and Quality Workflows
golangci-lint.yamlfor Go linting,codegen-check.yamlto ensure generated code is up to date,PRBuild.yamlfor building and validating pull requests,release.yamlfor automated releases with provenance attestation,scorecard.ymlfor supply chain security analysis,REUSE.yamlfor license compliance,stale.ymlfor managing stale issues and PRs. [1] [2] [3] [4] [5] [6] [7]Project Metadata and Configuration
.fabrica.yamlto define project metadata, enable code generation features (validation, events, conditional logic, storage, etc.), and configure build and generation settings for the Fabrica toolchain.These changes collectively establish a strong foundation for automated quality assurance, reproducibility, and compliance in the development process.
For more info, see Contributing Guidelines.