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

Automate moving of the stable branches #385

Open
4 tasks
lachmanfrantisek opened this issue Oct 12, 2022 · 1 comment
Open
4 tasks

Automate moving of the stable branches #385

lachmanfrantisek opened this issue Oct 12, 2022 · 1 comment
Labels
complexity/epic Lost of work ahead, planning/design required.

Comments

@lachmanfrantisek
Copy link
Member

lachmanfrantisek commented Oct 12, 2022

We'd like to automate moving the stable branches and creating a blog post so that the scripts don't need to be run locally.

Definition of done:

  • moving of the stable branches and creation of the weekly packit.dev blog posts are run in a Github action
    • the work that is currently done by running a script locally will be moved to a GitHub action that can be triggered manually in Github UI (=> the script can run non-interactively)
    • the PR with the blog post will be opened automatically by running the action and the content can be modified by a person
  • instructions for the Service Guru role are updated

When this is done, our team will benefit from elimination of human errors during the process.

@lachmanfrantisek lachmanfrantisek added the complexity/epic Lost of work ahead, planning/design required. label Oct 12, 2022
@lachmanfrantisek lachmanfrantisek transferred this issue from packit/packit-service Oct 12, 2022
@lachmanfrantisek lachmanfrantisek moved this from new to refined [10] in Packit Kanban Board Oct 12, 2022
@lachmanfrantisek
Copy link
Member Author

After a team discussion, we didn't pick this as a top Packit team priority for the next quarter and preferred epics with bigger user benefits. (Sadly, we have limited resources...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity/epic Lost of work ahead, planning/design required.
Projects
Status: refined
Development

No branches or pull requests

1 participant