Extend Merge Options #217
No reviewers
Labels
No Label
Priority-high
Accepting-merge-requests
API
API-dependency
Backport
Blocked
Brainstorming
Breaking
Bug
Changelog
CI
Cleanup
Confirmed
Discussion
Documentation
Duplicate
Enhancement
External-dependecy
F-droid
Feature
Google-play
Improvement
Invalid
Investigate
LGTM-done
LGTM-need
Long-term
Major-release
Minor-release
Needs-cleanup
Needs-feedback
Needs-help
Priority-critical
Priority-low
Priority-medium
Question
Ready
Refactor
Regression
Release
Repository
Security
Suggestion
Support
Testing
Translation
UI/UX
Upstream
Website
WIP
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#217
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "6543/GitNex:extend-merge-dialog"
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?
close #212
@ -16,3 +29,4 @@
this.MergeTitleField = MergeTitleField;
}
public enum Mode{
space
Mode {
this is ready it (if you mean functionalety).
but the Spinner doesnt look nice and it doesnt use translation for the displayed options ... didn't find a easy solution for this :(
@mmarif do you know how to do this UI stuff?
@6543 sure, I will check the ui if it need tweaks I will do otherwise will merge.
@ -19,0 +32,4 @@
public enum Mode{
Merge, //merge
Rebase, //rebase
RebaseMerge, //rebase-merge
I believe this could be handled properly without enum as it is suppose to be
Rebase (--no-ff)
. I guess its best to be handled in strings than here. In that case this PR might need some work to rewrite the code.I used an enumbe because api only allow this strings it doesnt ofward the argument to git its an option of the api with 4 posible strings
I am thinking of to have
key:value
type like in dialog box, spinner etc. That way can have more control over the values and keys can be kept as is to send to the API.[WIP] Extend Merge Optionsto Extend Merge OptionsI'll removed the WIP in fafour of the lable - and to be able to use the update button
Ok, makes sense.
@6543 for most of the part everything works. UI match the app style.
From my tests on 1.11, squash and rebase-merge throw 500 errors. Maybe you can check on your side.
@mmarif I'll look into the git log when these options where added if they are added lately I'll add a version check
I'll thest this in gennerel :)
EDIT: this options are included in 1.11.x
EDIT: they where added before v1.8.0; I can't tell you when exactly but this is pointles
I am on 1.11.3 and getting 500.
ToDo: add a Title text field and PreFill it with Pull Title and Pull Number:
Pulltitle (#number)
after Pull Title is added I considder it as ready.
@mmarif I'll try to add it :)
Note: enable squash-merge only on v1.11.5 and higher
(https://github.com/go-gitea/gitea/pull/11039)
If we add Gitea version check, is this still needed to add title?
squash and rebase-merge both. Can be done in the setMergeAdapter() function.
removed wrong lable 😅
-> to
616a101fe7
Android Studio suggested me this change but I don't know what to think of ..@mmarif I considder this as ready 🎉 🎆
I have pushed some minor changes. Ready from my side.
Should I merge now?
looked at your changes - nothing against them to say -this pull is ready 🚀 @mmarif