[UI Improvements] collect ideas from the gitnex community #319
Labels
No Label
⌚ Major-release
⌚ Minor-release
⚔️ Wontfix
⚙️ CI
⛏️ Breaking
✨ Duplicate
❌ Invalid
❓ Question
❤️ Support
➡️ Frontport
➡️ Needs-frontport
🔙 Backport
💭 Brainstorming
🐛 Bug
🔭 Cannot-reproduce
🧺 Cleanup
🧾 Confirmed
💬 Discussion
📄 Documentation
🎯 Enhancement
🩹 External-dependecy
📱 F-droid
🎉 Feature
👋 Good-first-issue
🤾 Google-play
🔙 Has-backport
🚀 Improvement
🚨 Investigate
🌠 Long-term
🔙 Needs-backport
🧺 Needs-cleanup
📡 Needs-feedback
📈 Performance
📌 Priority-critical
📌 Priority-high
📍 Priority-low
📍 Priority-medium
🥑 Ready
🪒 Refactor
🔙 Regression
📸 Release
🔒 Security
💡 Suggestion
🧪 Testing
🌐 Translation
💻 UI/UX
🪜 Upstream
🟦 Website
🙇♂️ Needs-help
🛰️ API-dependency
🛡️ Blocked
🏗️ Build
🗒️ Changelog
🗄️ Repository
🗓️ Summary
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#319
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
as title - each comment an idear
Once the idea is confirmed, new issue will be created and task should be updated to done here with link to issue.
Add option in settings to add repositories of "Organisations" to "My repositories"
Specify what you're about to search in the search bar as hint (e.g. 'Search repositories', 'Search issues', etc.).
Built-in text editor.
Making issue
tagslabels a little bit smaller and proportional.Nice idea, you can send a PR. Check how it is done(it's diff than default FAB) in repos etc.
Starred repos works that way I guess?
My repositories are termed as repositories under your namespace. We can introduce something like
Favourates
for app only. But I am afraid it will create alot of confusions for users. My repos, starred repos, favourates.This is changed in commits PR(if I am not mistaken). It's generic search icon now. Every screen has its own search filter, so adding extra text is redunt to me.
To edit/add new items something like Rich text editor?
By tags you mean labels, which you already send a PR.
Thanks for the valuable inputs. I appreciate it.
I will have a look into that, but as before, i can't promise anything.
I found it very confusing to search using the search bar, because it does not clearly state (as a hint, placeholder) what you're about to search. It just says "Search...". I think it would be more clear to use "Search pull requests..." on the pull request screen and so on ("Search open issues...", "Search milestones...").
Exactly.
Imagine you have more than multiple repos in one oranization. It would be a hassle to add each repo one by one to "starred repositories".
No rush
This could be discussed more once local db implemented. Because this is going to be app only feature. Also need a better name for this.
I will add the valid points to the main post for future implementation.
Add link to commits on master branch to the first page "Details" of any repo.
Display number of commits (master) on "Default"-page but also on each branch under "Branches"
Add "commits since this release".
Created By: @meena
I'd also like to see a switch for different Branches in the files Browser — and whereever else that applies.
There's currently no way to read code anywhere other than the main branch.
it should be easier to visually distinguish issues from PRs (even without #332)
Title: Render READMEs while browsing files
Idea: When browsing files, if a file named
README.md
is present at any level of a repo, render the markdown of the readme below the files.Today, Gitnex renders only the top level README, in the Overview section. Browsing files section, we are two taps away from the most human readable version of the the readme (tap to open file, tap to render as markdown).
See Github on web. Having a readme at each level makes repositories more navigable, especially if complicated, contain many components that deserve a README.