You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I much prefer working in PHP than GitHub actions, so what I'm imagining here is being able to write some of the other steps of my preview workflow as classes that can be added to the pipeline. Maybe with hooks to add classes before and after the existing pipeline, or by overriding existing classes like in laravel-shift/blueprint.
For example instead of GitHub issues we use Linear. The Linear/GitHub integration is a great start, but I have a few other steps that I use;
Check the PR relates to a Linear issue
provision
update linear issue status and comment with preview url
I don't have the skill to PR this, but if @mehrancodes would accept something like this I'd be happy to sponsor the work.
The text was updated successfully, but these errors were encountered:
Having the Linear integration looks fantastic! I think it would be nice to have some hooks during the provision/teardown process as there are still many custom setups we may need to have based on the project's requirements.
Also, extensions installable via composer could be the perfect fit. As everyone can add their steps and even share their use-case publicly!
I think this one is possible by introducing a new environment variable accepting an array of installed packages - and maybe the step where you would like to use this package. Any thoughts?
I much prefer working in PHP than GitHub actions, so what I'm imagining here is being able to write some of the other steps of my preview workflow as classes that can be added to the pipeline. Maybe with hooks to add classes before and after the existing pipeline, or by overriding existing classes like in
laravel-shift/blueprint
.For example instead of GitHub issues we use Linear. The Linear/GitHub integration is a great start, but I have a few other steps that I use;
I don't have the skill to PR this, but if @mehrancodes would accept something like this I'd be happy to sponsor the work.
The text was updated successfully, but these errors were encountered: