postgresql: enable parallel build #7

tek · 2024-03-15T14:00:43+01:00

tek commented

2024-03-15 14:00:43 +01:00

content signing missing

👍 1 👀 1

tek added 1 commit 2024-03-15 14:00:43 +01:00

6311aa9f96 postgresql: enable parallel build

tb changed title from ~~WIP: postgresql: enable parallel build~~ to postgresql: enable parallel build

2024-03-15 15:52:28 +01:00

tb added 1 commit 2024-03-15 16:03:22 +01:00

93fe749c9f

postgresql: updated signature

tb merged commit 910af7a38d into 3.7

2024-03-15 16:05:11 +01:00

tb referenced this issue from a commit

2024-03-15 16:05:12 +01:00

postgresql: enable parallel build (#7)

tb commented

2024-03-15 16:10:03 +01:00

Hey tek!

Thank you for your submission and the opportunity to test out how to handle PRs, so I will try to document what I did.

The instructions as shown here on the pull request page

do not work quite well.
You are shown as the commits author, but the PR will remain open:

I ran

git reset --soft HEAD~2; git restore --staged .
git push --force

to erase that from the git history again.
Instead, I cloned your forked repo, updated the key and pushed that back to your fork.
After that I was able to do a squash commit over the gitea pull request ui.

I am sure there can be a more neater way, but I will need to test this on the next pull request!

Again, thank you very much!

Hey tek! Thank you for your submission and the opportunity to test out how to handle PRs, so I will try to document what I did. The instructions as shown here on the pull request page ![image](/attachments/1f239026-ba42-4a1a-a3e0-55ca7f8169bb) do not work quite well. You are shown as the commits author, but the PR will remain open: ![image](/attachments/c472fbaa-7325-4d52-a5d1-0898e21635b9) I ran ``` git reset --soft HEAD~2; git restore --staged . git push --force ``` to erase that from the git history again. Instead, I cloned your forked repo, updated the key and pushed that back to your fork. After that I was able to do a squash commit over the gitea pull request ui. I am sure there can be a more neater way, but I will need to test this on the next pull request! Again, thank you very much!

image.png

18 KiB

Sign in to join this conversation.

No reviewers