Updated credits and contributing #3413
No reviewers
Labels
No Label
#P1 CRITICAL
#P2: HIGH
#P3: elevated
#P4 priority: medium
#P6: low
#Review
annoying
API
bug
code quality
combat
commands
compatibility
configurability
contribution inside
controls
core feature
creative mode
delayed for engine release
documentation
duplicate
enhancement
environment
feature request
gameplay
graphics
ground content conflict
GUI/HUD
help wanted
incomplete feature
invalid / won't fix
items
looking for contributor
mapgen
meta
mineclone2+
Minecraft >= 1.13
Minecraft >= 1.17
missing feature
mobile
mobs
mod support
model needed
multiplayer
Needs adoption
needs discussion
needs engine change
needs more information
needs research
nodes
non-mob entities
performance
player
possible close
redstone
release notes
schematics
Skyblock
sounds
Testing / Retest
tools
translation
unconfirmed
mcl5
mcla
Media missing
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: VoxeLibre/VoxeLibre#3413
Loading…
Reference in New Issue
No description provided.
Delete Branch "translation_credit_anarquimico"
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?
Updated credits etc.
I'm glad that you added @anarquimarco into the credits. (For the translation credits.)
Gitea implied I could rebase the branch on his fork, and I couldn't and after that fork information was broken and I couldn't even merge it. Finally got around to creating a separate branch and merging it in.
The
rebase
command seems pretty hinky and quite prone to causing havoc.Hinky? Its a bit hard to use, but its great once you learn how to use it. Its also required to fix merge issues so you can merge.
The rebase is fine. This isn't a git issue. It's a gitea issue. Gitea allows you to try and rebase when you don't have access and it gets into a weird state it shouldn't where the PR data gets messed up.
One gitea issue I noticed is if you use the rebase button, it will say broken fork information. If you refresh it, it will start the merge issue checker.
Yeah, most of the time that does the trick, but not always.
nods hinky. Most of my experience with it, is through Gitea... and that's where I learned that if you really want to hose things and make the branch horribly broken... use rebase.
I've not had that be successful.
What has worked well, is doing rebase in something other than Gitea.
I've not been lucky enough to have this work, so my perception of it's viability could be skewed due to personal experience.
Also, I forgot to mention, but when you need to update the branch after you rebase from gitea, you need to delete the local branch and check it out again. I think this PR might end up being the knowledge of the works of rebasing discussion for future coders 😏.
That is indeed, very helpful knowledge.