ports/contrib
3
3
Fork 2
Code Issues Pull Requests Activity

postgresql: enable parallel build #7

Merged
tb merged 2 commits from tek/contrib-tek:3.7 into 3.7 2024-03-15 16:05:11 +01:00
Conversation 1 Commits 2 Files Changed 2 +3 -3
tek commented 2024-03-15 14:00:43 +01:00
Contributor
Copy Link

content signing missing

content signing missing
👍 1 👀 1
tek added 1 commit 2024-03-15 14:00:43 +01:00
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
tb merged commit 910af7a38d into 3.7 2024-03-15 16:05:11 +01:00
tb commented 2024-03-15 16:10:03 +01:00
Owner
Copy Link

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
do not work quite well.
You are shown as the commits author, but the PR will remain open:
image

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.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ports/contrib#7
No description provided.
Delete Branch "tek/contrib-tek:3.7"

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?