Please include a summary of the changes and which issue is fixed. Include relevant motivation and context.
Fixes # (issue)
Please delete options that are not relevant.
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation update
- Performance improvement
- Code refactoring
- Tests
- CI/CD changes
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
- Test A
- Test B
Test Configuration:
- Python version:
- OS:
- MEGAGENT version:
- My code follows the style guidelines of this project
- I have performed a self-review of my own code
- I have commented my code, particularly in hard-to-understand areas
- I have made corresponding changes to the documentation
- My changes generate no new warnings
- I have added tests that prove my fix is effective or that my feature works
- New and existing unit tests pass locally with my changes
- Any dependent changes have been merged and published in downstream modules
- I have checked my code and corrected any misspellings
- I have updated CHANGELOG.md with my changes
Add screenshots to help explain your changes.
Add any additional notes or context about the pull request here.
If this PR introduces breaking changes, please describe them and the migration path for existing users.
List any new dependencies required for this change.
Any specific areas you'd like reviewers to focus on?
github: ELMOURABEA patreon: ELMOURABEA open_collective: ELMOURABEA ko_fi: ELMOURABEA liberapay: ELMOURABEA polar: ELMOURABEA buy_me_a_coffee: ELMOURABEA custom: ["https://github.com/sponsors/ELMOURABEA"] name: CI
on:
push: pull_request: branches: ["main"]
workflow_dispatch:
jobs:
build: # The type of runner that the job will run on runs-on: ubuntu-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v4
# Runs a single command using the runners shell
- name: Run a one-line script
run: echo Hello, world!
# Runs a set of commands using the runners shell
- name: Run a multi-line script
run: |
echo Add other actions to build,
echo test, and deploy your project.
name: Python package (Conda)
on: push: branches: [ main ] pull_request: branches: [ main ]
jobs: build: runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up Miniconda
uses: conda-incubator/setup-miniconda@v3
with:
python-version: '3.11'
auto-update-conda: true
activate-environment: activbot-ci
environment-file: environment.yml
use-mamba: true
- name: Install dependencies (fallback)
if: failure() || success()
run: |
python -m pip install --upgrade pip
pip install -r requirements.txt || true
pip install -r requirements-dev.txt || true
- name: Lint
run: |
if command -v flake8 >/dev/null 2>&1; then
flake8 . || true
fi
- name: Run tests
run: |
if command -v pytest >/dev/null 2>&1; then
pytest -q || true
fi
💼 **Open Collective:** [ELMOURABEA](https://opencollective.com/ELMOURABEA)
- 🎨 Ko-fi: ELMOURABEA
- 📺 Patreon: ELMOURABEA
- ⚡ Polar: ELMOURABEA
⭐ Star my repositories if you find them useful!
💖 Every contribution helps make open source sustainable!
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Examples of behavior that contributes to a positive environment for our community include:
- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall community
Examples of unacceptable behavior include:
- The use of sexualized language or imagery, and sexual attention or advances of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement through GitHub issues or direct contact with project maintainers.
All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community.
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
name:-Run-Gemini-CLIgoogle-github-actions/[email protected] gh repo clone google-gemini/gemini-cli
Thank you for your interest in contributing to the Economic Storm Platform! 🎉
- Fork the Repository: Click the "Fork" button at the top right
- Clone Your Fork:
git clone https://github.com/YOUR_USERNAME/Economic-Storm-platform.git cd Economic-Storm-platform - Create a Branch:
git checkout -b feature/your-feature-name
-
Create an Issue First: Use our issue templates
- Business Development Task
- Platform Development Task
- Marketing Task
-
Work with Copilot: Leverage GitHub Copilot for assistance
- Code generation
- Documentation
- Testing
-
Follow Best Practices:
- Write clear, readable code
- Add comments where necessary
- Update documentation
- Add tests if applicable
-
Commit Your Changes:
git add . git commit -m "Brief description of changes"
-
Push to Your Fork:
git push origin feature/your-feature-name
-
Create a Pull Request:
- Go to the original repository
- Click "New Pull Request"
- Select your branch
- Fill in the PR template
- Submit for review
- Reference the issue number (e.g., "Fixes #123")
- Provide clear description of changes
- Ensure CI/CD passes
- Respond to review feedback
- Keep PRs focused and small
- Use appropriate templates
- Provide clear titles with prefixes:
[BUSINESS]for business development[DEV]for platform development[MARKETING]for marketing tasks
- Fill all required fields
- Add relevant labels
- Specify Copilot Agent assistance needed
- Open: Issue is created
- Labeled: Auto-labeled by Copilot Agent
- Assigned: Someone takes ownership
- In Progress: Work begins
- Review: Work is reviewed
- Closed: Issue is completed
- Follow existing code patterns
- Use meaningful variable names
- Keep functions small and focused
- Comment complex logic
- Remove debug code before committing
- Write tests for new features
- Ensure existing tests pass
- Aim for good test coverage
- Test edge cases
- Update README if needed
- Document public APIs
- Add inline comments for complex code
- Keep CHANGELOG updated
- Clear Context: Provide clear problem descriptions
- Review Suggestions: Always review Copilot suggestions
- Iterate: Use suggestions as starting points
- Learn: Understand the code Copilot generates
- ✅ Boilerplate code
- ✅ Documentation
- ✅ Test cases
- ✅ Code explanations
- ✅ Refactoring suggestions
⚠️ Security-critical code⚠️ Complex algorithms⚠️ Business logic⚠️ Production configurations
Always review and test Copilot-generated code!
- Be respectful and constructive
- Focus on the code, not the person
- Explain your reasoning
- Suggest improvements
- Approve when ready
- Be open to feedback
- Respond to comments
- Make requested changes
- Ask questions if unclear
- Thank reviewers
- New features
- Bug fixes
- Performance improvements
- Refactoring
- README updates
- Code comments
- Tutorials
- API documentation
- Unit tests
- Integration tests
- End-to-end tests
- Test documentation
- Market research
- Business strategy
- Marketing content
- Partnership proposals
- Don't commit secrets or credentials
- Don't break existing functionality
- Don't ignore CI/CD failures
- Don't submit untested code
- Don't skip documentation updates
- README.md - Project overview
- COPILOT_GUIDE.md - Copilot collaboration
- WORKFLOW.md - Development workflow
- Check existing issues and discussions
- Create a new issue if needed
- Tag maintainers for urgent issues
- Join community discussions
Contributors will be:
- Listed in project acknowledgments
- Credited in release notes
- Recognized in the community
- Be respectful and inclusive
- Welcome newcomers
- Give constructive feedback
- Focus on collaboration
- Have fun building together!
Before submitting a PR, ensure:
- Code follows project style
- Tests pass locally
- Documentation is updated
- Commit messages are clear
- PR description is complete
- Issue is referenced
- No merge conflicts
- CI/CD passes
Your contributions help make Economic Storm Platform better for everyone!
Questions? Create an issue or reach out to maintainers.
Happy Contributing! 🚀✨