phpmentors-jp / workflower-bundle Goto Github PK

• Create 1.4 branch for the release if it does not exist
• Change the branch of the build status in README.md if the branch is newly created (1.4)
• Change README.md on the release branch. (1.4)
• Tag to the release on git with the command git tag -s v1.4.0 HEAD (1.4)
• Push changes to GitHub with the command git push upstream 1.4 and git push upstream --tags (1.4)
• Create a new draft release as PHPMentorsWorkflowerBundle 1.4.0 (stable) (GitHub)
• Publish the release
• Update wiki pages (Home)
• Update the version in README.md and composer.json from 1.4 to 1.5 if 1.4 branch is newly created (master)
• Push changes to GitHub with the command git push upstream master (master)
• Remove unnecessary releases in Packagist
• Remove unnecessary branches in GitHub
• Tweet the release

• Create 1.2 branch for the release if it does not exist
• Change the branch of the build status in README.md if the branch is newly created (1.2)
• Change README.md on the release branch. (1.2)
• Tag to the release on git with the command git tag -s v1.2.0 HEAD (1.2)
• Push changes to GitHub with the command git push upstream 1.2 and git push upstream --tags (1.2)
• Create a new draft release as PHPMentorsWorkflowerBundle 1.2.0 (stable) (GitHub)
• Write the description of the release
  • The release date in UTC TZ=UTC date
• Publish the release
• Update wiki pages (Home)
• Update the version in README.md and composer.json from 1.2 to 1.3 if 1.2 branch is newly created (master)
• Push changes to GitHub with the command git push upstream master (master)
• Remove unnecessary releases in Packagist
• Remove unnecessary branches in GitHub
• Tweet the release

• Create 1.3 branch for the release if it does not exist
• Change the branch of the build status in README.md if the branch is newly created (1.3)
• Change README.md on the release branch. (1.3)
• Tag to the release on git with the command git tag -s v1.3.0 HEAD (1.3)
• Push changes to GitHub with the command git push upstream 1.3 and git push upstream --tags (1.3)
• Create a new draft release as PHPMentorsWorkflowerBundle 1.3.0 (stable) (GitHub)
• Publish the release
• Update wiki pages (Home)
• Update the version in README.md and composer.json from 1.3 to 1.4 if 1.3 branch is newly created (master)
• Push changes to GitHub with the command git push upstream master (master)
• Remove unnecessary releases in Packagist
• Remove unnecessary branches in GitHub
• Tweet the release

Hi! Thank's for library. But, I can't understand how it use. Can you provide some examles?

A WorkflowContext object will be used instead of a bare workflow ID. It can be get by using Process::getWorkflowContext(). (1f28445)

Hello, I'm try to start a new symfony project with workflowerBundle and symfony 2.7.3 , but i have a little problem

my composer file:
"phpmentors/workflower": "^1.0",
"phpmentors/workflower-bundle": "^1.0"

my AppKernel :
...
new PHPMentors\WorkflowerBundle\PHPMentorsWorkflowerBundle()

in my app/config/services.yml

imports:
- { resource: "@PHPMentorsWorkflowerBundle/Resources/config/services.xml" }

but when I try run my app generate the next problem

RuntimeException in CheckReferenceValidityPass.php line 100: The definition "phpmentors_workflower.doctrine_lifecycle_listener" has a reference to an abstract definition "phpmentors_workflower.workflow_serializer". Abstract definitions cannot be the target of references.

can you help me?, I will like create a new application using your great bundle

do you have a little example working with your bundle?

regards!

• Create 1.1 branch for the release if it does not exist
• Change the branch of the build status in README.md if the branch is newly created (1.1)
• Change README.md on the release branch. (1.1)
• Tag to the release on git with the command git tag -s v1.1.0 HEAD (1.1)
• Push changes to GitHub with the command git push upstream 1.1 and git push upstream --tags (1.1)
• Create a new draft release as PHPMentorsWorkflowerBundle 1.1.0 (stable) (GitHub)
• Write the description of the release
  • The release date in UTC TZ=UTC date
• Publish the release
• Update wiki pages (Home)
• Update the version in README.md and composer.json from 1.1 to 1.2 if 1.1 branch is newly created (master)
• Push changes to GitHub with the command git push upstream master (master)
• Remove unnecessary releases in Packagist
• Remove unnecessary branches in GitHub
• Tweet the release

• Create 1.0 branch for the release if it does not exist
• Change the branch of the build status in README.md if the branch is newly created (1.0)
• Change README.md on the release branch. (1.0)
• Tag to the release on git with the command git tag -s v1.0.0 HEAD (1.0)
• Push changes to GitHub with the command git push upstream 1.0 and git push upstream --tags (1.0)
• Create a new draft release as PHPMentorsWorkflowerBundle 1.0.0 (stable) (GitHub)
• Write the description of the release
  • The release date in UTC TZ=UTC date
• Publish the release
• Update wiki pages (Home)
• Update the version in README.md and composer.json from 1.0 to 1.1 if 1.0 branch is newly created (master)
• Push changes to GitHub with the command git push upstream master (master)
• Remove unnecessary releases in Packagist
• Remove unnecessary branches in GitHub
• Tweet the release

Hi

Whats the development status of this and phpmentors-jp/workflower?
This 2 project still maintained?
Is update for symfony 5.x/6.x and PHP ^8.0 planed?

Thx