Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Semantic Release workflow for Jeedom Plugins #62

Closed
wants to merge 3 commits into from

Conversation

pifou25
Copy link
Contributor

@pifou25 pifou25 commented Nov 26, 2023

Workflow Semantic-Relese

Gère automatiquement le numéro de version du repo, sur les branches master et beta.

https://community.jeedom.com/t/semantic-release-et-le-versioning-automatique/112008

Modifications automatiques gérées:

  • pluginVersion dans le fichier plugin_info/info.json
  • le changelog master (liste des commits et liens) sur la branche master, et les versions.
  • le changelog beta, sur la branche beta uniquement
  • et puis c'est tout

Nécessite d'ajouter la permission "write" sur le workflow, car il push les modifications (changelog, numéro de version...) sur un commit distinct.

Suggested changelog entry

Le titre du commit sera automatiquement reporté dans le changelog

Types of changes

  • Bug fix (non-breaking change which fixes)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
    • This change is only breaking for integrators, not for external standards or end-users.
  • Documentation improvement
  • CI/CD improvment

PR checklist

  • I have checked there is no other PR open for the same change.
  • I have read the Contribution Guidelines.
  • I grant the project the right to include and distribute the code under the GNU.
  • I have added tests to cover my changes.
  • I have verified that the code complies with the projects coding standards.
  • [Required for new sniffs] I have added MD documentation for the sniff.

@pifou25 pifou25 closed this Nov 26, 2023
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.

3 participants