Would require leveraging an existing secondary branch or creating a temporary branch. This is platform specific, with a focus on GitHub for now.
Desired user experience
- User has two existing and formal branches, the user will decide which branch to merge into and from. Upon selecting the source and destination, the user should be able to create a PR with some level of detail within the GUI. Level of complexity may increase depending on if we want to support Markdown preview (and whether the respective platform's CLI can support this level of complexity)
- User has one branch they want to merge into. A temporary branch will be created to support the creation of a PR and immediately deleted after. Has similar complexity issue as the first point.
Alternative to MD preview complexity is providing the user with the link to the PR with some details prefilled (allegedly supported by some platforms' CLIs)
My apprehension with more complexity is: if we are continuously adding "QoL" features, at some point we are just approaching the complexity of IDE extensions or formal platform apps. It's important to add features while focusing on what makes Guck "Guck," i.e., the simplicity and minimalistic UI. If the user wants a dedicated app, they have other options.
Was blocked by #3 (now implemented)
Would require leveraging an existing secondary branch or creating a temporary branch. This is platform specific, with a focus on GitHub for now.
Desired user experience
Alternative to MD preview complexity is providing the user with the link to the PR with some details prefilled (allegedly supported by some platforms' CLIs)
My apprehension with more complexity is: if we are continuously adding "QoL" features, at some point we are just approaching the complexity of IDE extensions or formal platform apps. It's important to add features while focusing on what makes Guck "Guck," i.e., the simplicity and minimalistic UI. If the user wants a dedicated app, they have other options.
Was blocked by #3 (now implemented)