[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] branches and projects
|
On Wed, Feb 15, 2012 at 17:55, Thomas Hallgren <thomas@xxxxxxx> wrote:
> Hi,
>
> When working with branches it's not uncommon that one branch contains
> projects that doesn't exist in another branch. Switching between the two
> will then mess up the workspace. Ideally, I'd like to somehow associate
> projects with branches so their presence in the workspace would depend on
> what branch I'm looking at. Is this something that has been considered as an
> egit feature?
>
> Regards,
> Thomas Hallgren
>
> _______________________________________________
> egit-dev mailing list
> egit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/egit-dev
I am working on a similar feature, where i want to associate Mylyn
tasks to Git branches. The goal is to support a workflow with feature
branches per task (or one branch for multiple tasks, like stories or
epics) like this:
- Activate a Mylyn task
- If there is a context with a psf for that context, check out the
appropriate branches
- on task deactivation save a PSF for the context (i.e., all projects
with their repositories and the currently checked out branch will be
exported as PSF and saved in the task
For that feature, it is necessary to rewrite the persistence model of
Mylyn task and context. I started with that, but can't provide any
timeframe.
The bugs for that feature are
https://bugs.eclipse.org/bugs/show_bug.cgi?id=358554 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=345661
But i could imagine, that it would be possible to implement your
suggestion (the associations could be persisted within the new Mylyn
persistence), once that requirements are done.
Regards,
Manuel
