Comments (7)
FINK-11 No PR button in LitFloat after direct pushes
from inlang-fink.
@felix.haeberle You raised this issue.
It is complicated to resolve this:
- If you are the repo's owner and your repo is not a fork, there will be no PR button in the LixFloat.
- Fink expects all repos that are forks to open PRs back to the parent repo. This is based on the PR workflow where fork first and contribute back.
- Tracking the flow from the parent repo to pr and seems unreliable. If you reopen your fork directly and want to open a PR, users have to use GitHub for that.
Possible proposals
- Atm, if you fork should diverge from the parent, you can just ignore the fork button and continue.
- The alternative would be to flag a repo for inlang apps that it should diverge. Atm this is only needed for Fink as it is the only app with PR workflow from the browser, so save this to the local storage.
- Introducing a different process where users have to proactively open forks with the risk of outdated and unmerged forks.
IMO 2. is the way to go for now. Let the 2% flag their repo in the settings and force the 98% to use PRs non-techs need to learn this process.
In the long run, we need those flags in the SDK and redesign the pull request flow in a way that users don't need to think about it because it happens in the background.
from inlang-fink.
After a few more thoughts.
Ideal UX
If I'm part of the team, I open the project, make my changes and it should be commited, when I'm done. (To support autosaving, these changes are collected and commited, when the user is done. The lix server might help with that in the future. Also for live collaboration)
I just open the file, make my changes and click request changes, if I'm not part of the team. The team is notified and can decide to add this changes. (fork + pr workflow in the background)
If I want this file to diverge, I want to click copy. Maybe I we can offer features like, "get updates from the original" or "merge documents", but since the copy action was done, we don't assume PRs anymore and users explicitly state that the copy should be updated or merged with main. (same forking + pr workflow as well, but with explicit user actions)
from inlang-fink.
@niklas.buchfink is this not partially
solved by our conditional modal that allows deactivating notifications about diverging forks? if i activate this it is a frok that should diverge, if not i want to usually contribute back eventually.
from inlang-fink.
i always see there are these options after making changes in fink:
- push the changes back to the same branch
- submit for review: if it is a fork, select if on my fork or for the upstream
from inlang-fink.
@jan.johannes You are right; we can use the tick from the modal as a condition for this flow 👍
The "Ideal UX" I illustrated above is an idea of hiding much of the git-specific workflows and terms from non-technical users and creating something they can understand. Does this make sense for an app contribution workflow for non-techs (in the long term)?
from inlang-fink.
I implement the suggested behaviour that no pull request status is displayed in the LixFloat if the user has ticked to deactivate notifications about diverging forks.
from inlang-fink.
Related Issues (20)
- add supported i18n libraries to fink product page HOT 11
- public repo can't be opened HOT 3
- the doc won't let me push changes HOT 4
- Not able to push translations HOT 4
- Show displayNames of language in Fink HOT 1
- Fink doesn't show me the other branches HOT 6
- Why did it add source-code in project dropdown | Fink HOT 3
- searchable projects HOT 1
- search for branches HOT 1
- save last selected project HOT 1
- Make PushException in Fink consistent
- Test issue
- Failed to push changes HOT 2
- forking errors with 404 HOT 1
- Improve workflow conditions based on repo meta infos HOT 4
- focus project selection on project names instead of path/to/inlang.project to reduce cognitive load HOT 1
- Newlines not committed correctly in fink HOT 3
- fink can't open repos anymore HOT 4
- Inconsistent behavior for letter-casing in adding language in Fink and paraglide-init HOT 2
- decide on tech stack HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from inlang-fink.