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

Produce a workflow on how to manage the version using the github action. #12

Open
2 tasks
darwinsubramaniam opened this issue Jul 12, 2020 · 2 comments
Open
2 tasks
Assignees
Labels
enhancement New feature or request gitflow
Milestone

Comments

@darwinsubramaniam
Copy link
Contributor

darwinsubramaniam commented Jul 12, 2020

Using the github action , the version bump workflow should be created .

  • Create Wiki to define how the Version works for this project

  • Define how the github action will automate the process of version bumping

@darwinsubramaniam darwinsubramaniam created this issue from a note in Roadmap V0.1 (In progress) Jul 12, 2020
@darwinsubramaniam darwinsubramaniam added this to the 0.1 milestone Jul 12, 2020
@darwinsubramaniam
Copy link
Contributor Author

There is one Automated Version Bump action found Github Action. Using this can enable automated checking based on the commit messages.

By applying this process the git commit message become very important to indicate if the version is major or minor release.

Workflow

Based on the commit messages, increment the version from the latest release.

  • If the string "BREAKING CHANGE" or "major" is found anywhere in any of the commit messages or descriptions the major version will be incremented.

  • If a commit message begins with the string "feat" or includes "minor" then the minor version will be increased.
    This works for most common commit metadata for feature additions: "feat: new API" and "feature: new API".

  • All other changes will increment the patch version.

  • Push the bumped npm version in package.json back into the repo.

  • Push a tag for the new version back into the repo.

@darwinsubramaniam darwinsubramaniam self-assigned this Jul 12, 2020
@darwinsubramaniam darwinsubramaniam added enhancement New feature or request gitflow labels Jul 12, 2020
@darwinsubramaniam
Copy link
Contributor Author

The above Automated Version Bump have shown the disadvantage of monorepo, this is dangerous especially when the changes is focused at one component. The version bump is taking place in overall project. This is undesirable. This brings the split of repository to have multiple plugins as respective repo. The one required work required is also a nest library for extractor plugin. This will ensure how the Task Scheduler will able to call the extractor to activate certain plugins .
This public API facing between the taskscheduler and the extractor should be finalized before starting the next development .
The public API facing between the taskscheduler and the AIFactory should also be finalized but this can be push to lower priority as the requirement of collecting the data have to be prioritized first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request gitflow
Projects
Roadmap V0.1
  
In progress
Development

No branches or pull requests

1 participant