Skip to content

Fix/workflow branch protection phase2#8

Merged
behrangsa merged 4 commits into
masterfrom
fix/workflow-branch-protection-phase2
Aug 27, 2025
Merged

Fix/workflow branch protection phase2#8
behrangsa merged 4 commits into
masterfrom
fix/workflow-branch-protection-phase2

Conversation

@behrangsa
Copy link
Copy Markdown
Contributor

No description provided.

This commit introduces a comprehensive GitHub Actions workflow that automates
the versioning and release process for keegees with the following features:

Automated Release Pipeline:
- Triggers on pushes to master branch with manual workflow_dispatch option
- Implements custom v-x.y.z tag format with automated patch version increments
- Creates both .tar.gz and .zip release archives with proper directory structure
- Generates professional release notes with installation instructions

Quality Assurance:
- Runs ShellCheck validation on keegees.sh and install.sh before releases
- Ensures code quality standards are maintained in automated releases
- Includes comprehensive error handling and validation steps

Release Management:
- Creates GitHub releases with detailed descriptions and usage examples
- Attaches source code archives for easy distribution
- Updates README version badges automatically
- Provides clear installation instructions and requirements

This workflow enables seamless automated releases while maintaining the
project's high quality standards and comprehensive documentation.
…nization and corrected baseline to v0.0.1

This commit significantly improves the automated release workflow and establishes proper version consistency across the entire codebase.

Workflow enhancements:
- Added comprehensive multi-file version synchronization that updates README.md version references and keegees.sh VERSION constant
- Implemented atomic commit functionality with [skip ci] tags to prevent recursive workflow triggers
- Enhanced workflow structure with proper step ordering and dependency management
- Added verification logging for all version update operations

Version baseline corrections:
- Fixed README.md CLI example version display: 1.0.0 → 0.0.1
- Fixed keegees.sh VERSION constant: 1.0.0 → 0.0.1
- Established consistent v0.0.1 baseline across git tags, GitHub releases, README.md, and keegees.sh

The enhanced workflow now ensures perfect version consistency across all project files and maintains the keegees project's professional standards with robust error handling and safety-first approach.
Cleaned up duplicate GitHub Actions workflow files by removing the obsolete
auto-tag-and-release.yml in favor of the comprehensive release.yml workflow.

The release.yml workflow contains all necessary functionality:
- Complete 10-step release process
- Proper vX.Y.Z version format throughout
- ADMIN_TOKEN configuration with GITHUB_TOKEN fallback
- Enhanced push strategy with --force-with-lease
- Dynamic version warning implementation
- Comprehensive setup documentation

This maintains clean CI/CD configuration while preserving all required
automation capabilities for the keegees project release process.
…ry rules

Simplified the release workflow authentication approach by removing ADMIN_TOKEN requirements:

- Removed comprehensive ADMIN_TOKEN documentation and setup requirements from workflow comments
- Reverted checkout step to use standard GITHUB_TOKEN instead of ADMIN_TOKEN fallback
- Removed --force-with-lease push strategy, returning to regular git push
- Removed environment variable override in tag creation step
- Streamlined workflow to standard GitHub Actions approach

This change is possible because repository rules have been relaxed to allow automated
workflows to function properly without requiring admin privileges to bypass protection rules.
@behrangsa behrangsa merged commit 34c6d1a into master Aug 27, 2025
1 check passed
@behrangsa behrangsa deleted the fix/workflow-branch-protection-phase2 branch August 27, 2025 20:45
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.

1 participant