gitea/blog
45
20
Fork 32
Code Issues 10 Pull Requests 2 Actions Activity

blog post about backporter #260

Merged
techknowlogick merged 2 commits from bp-to-the-future into main 2023-04-24 01:08:47 +00:00
Conversation 3 Commits 2 Files Changed 1 +17
techknowlogick commented 2023-04-19 18:17:23 +00:00
Owner
Copy Link

anyone else who made edits to this post, please feel free to add your name to authors :)

anyone else who made edits to this post, please feel free to add your name to authors :)
🎉 2
techknowlogick added 1 commit 2023-04-19 18:17:23 +00:00
blog post about backporter
All checks were successful
check-and-test / check-and-test (push) Successful in 1m19s
Details
check-and-test / check-and-test (pull_request) Successful in 1m12s
Details
continuous-integration/drone/pr Build is passing
Details
d4d2dc6ed6
website_pr_previewer_bot commented 2023-04-19 18:19:18 +00:00
First-time contributor
Copy Link

Website preview: http://preview-gitea-org-blog-blog-260.s3-website.eu-central-1.amazonaws.com/
Blog post: http://preview-gitea-org-blog-blog-260.s3-website.eu-central-1.amazonaws.com/2023/04/backports-to-the-future/

Website preview: http://preview-gitea-org-blog-blog-260.s3-website.eu-central-1.amazonaws.com/ Blog post: http://preview-gitea-org-blog-blog-260.s3-website.eu-central-1.amazonaws.com/2023/04/backports-to-the-future/
jolheiser approved these changes 2023-04-19 18:27:59 +00:00
jolheiser left a comment
Owner
Copy Link

Various nits, nothing huge, feel free to commit or discard them. 🙂

Various nits, nothing huge, feel free to commit or discard them. 🙂
content/post/backports-to-the-future.md Outdated
@ -0,0 +3,4 @@
author: "techknowlogick"
title: "Back(ports) to the future!"
draft: false
---
jolheiser commented 2023-04-19 18:20:39 +00:00
Owner
Copy Link

tags: ["backporter"]
Maybe not needed, but maybe handy in the future?

`tags: ["backporter"]` Maybe not needed, but maybe handy in the future?
jolheiser marked this conversation as resolved
content/post/backports-to-the-future.md Outdated
@ -0,0 +5,4 @@
draft: false
---
In working towards maintaining an LTS version of Gitea, one of the blockers was to be able to backport pull requests, for bug fixes and other changes.
jolheiser commented 2023-04-19 18:22:00 +00:00
Owner
Copy Link

was to be able to efficiently backport pull requests

Manual backports possible, just arduous, doubly so in the context of a potential LTS.

> was to be able to efficiently backport pull requests Manual backports possible, just arduous, doubly so in the context of a potential LTS.
jolheiser marked this conversation as resolved
content/post/backports-to-the-future.md Outdated
@ -0,0 +6,4 @@
---
In working towards maintaining an LTS version of Gitea, one of the blockers was to be able to backport pull requests, for bug fixes and other changes.
One of Gitea's maintainers, [yardenshoham](https://github.com/yardenshoham), in an effort to improve their development workflow created a tool to allow automation to create backports.
jolheiser commented 2023-04-19 18:23:47 +00:00
Owner
Copy Link

[...] created a tool to help automate backports.

> [...] created a tool to help automate backports.
content/post/backports-to-the-future.md Outdated
@ -0,0 +10,4 @@
A side-effect of this effort is that this tool can not only be used to backport just for his pull-requests, but most pull requests that need a backport too.
We are enormously thankful for his effort in creating this tool, as it has allowed numerous (a few hundred at last count) backports, and increased development velocity.
As well, with the tool being open source it has allowed others to provide enhancements.
jolheiser commented 2023-04-19 18:25:15 +00:00
Owner
Copy Link

I sort of want to make the quip about automating us out of a job, but maybe not in this post. 😁

I sort of want to make the quip about automating us out of a job, but maybe not in this post. 😁
jolheiser marked this conversation as resolved
content/post/backports-to-the-future.md Outdated
@ -0,0 +12,4 @@
We are enormously thankful for his effort in creating this tool, as it has allowed numerous (a few hundred at last count) backports, and increased development velocity.
As well, with the tool being open source it has allowed others to provide enhancements.
Feel free to check it out [here](https://github.com/GiteaBot/gitea-backporter).
jolheiser commented 2023-04-19 18:26:53 +00:00
Owner
Copy Link

Feel free to check out the repo.

Not a big deal, I just vaguely recall something about not using "here" for links.

> Feel free to check out [the repo](https://github.com/GiteaBot/gitea-backporter). Not a big deal, I just vaguely recall something about not using "here" for links.
jolheiser marked this conversation as resolved
jolheiser commented 2023-04-19 18:28:50 +00:00
Owner
Copy Link

Also thanks again @yardenshoham ❤️

Also thanks again @yardenshoham :heart:
techknowlogick added 1 commit 2023-04-19 18:31:14 +00:00
update with feedback
All checks were successful
continuous-integration/drone/pr Build is passing
Details
check-and-test / check-and-test (pull_request) Successful in 2m6s
Details
check-and-test / check-and-test (push) Successful in 2m11s
Details
delete closed PR preview s3 / delete_preview (pull_request) Successful in 19s
Details
85f283bbdd
techknowlogick commented 2023-04-19 18:32:43 +00:00
Author
Owner
Copy Link

Not a big deal, I just vaguely recall something about not using "here" for links.

Yes, you are right. Thanks for catching that. As when browsing links with screen readers if your link just says "here" it'll read solely that, so having more context aids in understanding what the link is.

I've made that edit, and the others too :)

> Not a big deal, I just vaguely recall something about not using "here" for links. Yes, you are right. Thanks for catching that. As when browsing links with screen readers if your link just says "here" it'll read solely that, so having more context aids in understanding what the link is. I've made that edit, and the others too :)
❤️ 1
yardenshoham approved these changes 2023-04-19 19:50:01 +00:00
yardenshoham left a comment
Member
Copy Link

❤️

:heart:
silverwind approved these changes 2023-04-19 22:54:29 +00:00
techknowlogick merged commit 586c97f7b0 into main 2023-04-24 01:08:47 +00:00
techknowlogick deleted branch bp-to-the-future 2023-04-24 01:08:47 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
jolheiser
yardenshoham
silverwind
Labels
Clear labels   
in progress

   
kind/bug

   
kind/deployment

   
kind/docs

   
kind/enhancement

   
kind/feature

   
kind/lint

   
kind/proposal

   
kind/question

   
kind/security

   
kind/testing

   
kind/translation

   
kind/ui

   
lgtm/done

   
lgtm/need 1

   
lgtm/need 2

   
priority/critical

   
priority/low

   
priority/maybe

   
priority/medium

   
reviewed/duplicate

   
reviewed/invalid

   
reviewed/wontfix

   
status/blocked

   
status/needs-feedback

   
status/wip
No Label
in progress
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need 1
lgtm/need 2
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/blog#260
No description provided.
Delete Branch "bp-to-the-future"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?