You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I've just noticed the new Draft Pull Requests Github feature has been enabled in this repo, so I think we should use it for translations pull requests on which we are still working (maybe together with the "work-in-progress" tag for "backwards compatibility").
Ciao Luca! I see your point but in terms of user experience for new contributors I prefer the issues.
They are just "plug-n-play" and people are used to them:
Pick the one you want by commenting that you want to work on that
When you are done, PR with a comment that says Closes #id_of_the_issue
💥 done
One way or the other we need to pick one approach, we can't have both because otherwise surely it's gonna be cluttered 🤣
As a side note, I'm surely going to use Draft Pull Requests for when I have to show a POC or something in other projects, instead of adding /wait, /pleasedontmergethiscacca or something. Good shout! 👍
Yeah, it's still pretty new, and I don't mind if people start using them in individual pull requests. If people get good mileage out of it I can add it as a suggestion to the maintainer guide.
Hi, I've just noticed the new Draft Pull Requests Github feature has been enabled in this repo, so I think we should use it for translations pull requests on which we are still working (maybe together with the "work-in-progress" tag for "backwards compatibility").
In other words, the workflow would be:
For an example of how this would work, please look at my new pull request (#118)
@tesseralis, @deblasis & @lssmn what do you think about it?
The text was updated successfully, but these errors were encountered: