+1 for protecting master from direct pushes
2022-03-25 16:09 skrev Andrey Loskutov:
I'm also in favour of requiring validation before push, but there
should be still possibility to manually merge anything.
We often have cases where builds aren't running at all, so to fix it
we have to be able
Op za 26 mrt. 2022 om 12:22 schreef Hannes Wellmann <
wellmann.hann...@gmx.net>:
> It is possible to move issues between repositories on GitHub, see [1], and
> it is also possible to link issues in other repositories by mentioning them.
>
> Although it is simpler for those that handle bugs to
Instead of creating more and more repositories, it would be better to
simply merge them to meaningful units.
Then one could simply create an organization readme where it explains
what problems should be reported to what sub project...
As one at the moment has to chose a component as well in
It is possible to move issues between repositories on GitHub, see [1], and it is also possible to link issues in other repositories by mentioning them.
Although it is simpler for those that handle bugs to assign them to the correct repository directly, I agree that it can be difficult to find
Thank you Aleksandar for the clarification I was searching for and the link to the foundation's exact plan (I just knew about the intention).
> I don't see anyone willing to spend the time to triage existing bugs in bugzilla and migrate them to GH issue when they make sense. Transitioning
On Sat., Mar. 26, 2022, 06:25 Wim Jongman, wrote:
> The transition team is making great progress.
>
> On behalf of everyone: Thank you all!
>
I second that!
Jonah
> Cheers, Wim
>
> On Fri, 25 Mar 2022 at 16:16, Mickael Istria wrote:
>
>> eclipse.platform.text Git repository is now moved
The transition team is making great progress.
On behalf of everyone: Thank you all!
Cheers, Wim
On Fri, 25 Mar 2022 at 16:16, Mickael Istria wrote:
> eclipse.platform.text Git repository is now moved to GitHub:
> https://github.com/eclipse-platform/eclipse.platform.text
> If you see this
Speaking from someone who only recently made a first contribution to
Eclipse, but has been using Eclipse for years and occasionally reported
issues, I have to say that already the many existing project are simply
confusing to pick from when a user simply wants to report something. The
bugzilla
On Sat, Mar 26, 2022 at 10:42 AM Hannes Wellmann
wrote:
> At the moment it is not clear to me (maybe I have missed something) if I
> should still use Bugzilla or instead the Github Issues of for
> Eclipse-projects that were moved to Github?
> IIRC to was not the plan to shutdown the associated
At the moment it is not clear to me (maybe I have missed something) if I should still use Bugzilla or instead the Github Issues of for Eclipse-projects that were moved to Github?
IIRC to was not the plan to shutdown the associated Bugzilla now, but does this also mean that bugs should still be
Andrey, you could merge your PR without waiting for the verification build
in exceptional cases.
Andrey Loskutov schrieb am Fr., 25. März 2022, 16:09:
> I'm also in favour of requiring validation before push, but there should
> be still possibility to manually merge anything.
> We often have
11 matches
Mail list logo
