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
{{ message }}
This repository has been archived by the owner on Jun 3, 2019. It is now read-only.
Hi @ctrlplusb, a question rather than an issue. As I was customizing a branch in my fork for my current needs, I realized that some other folks might have done similar things before, while others might have similar requirements.
So, that made me wonder if we should add a section to the Feature Branches page to have a section for 'Community maintained feature branches'?
Folks like me could add our feature branches that we intend to maintain with a short description on there and that would make it easy to circulate ideas.
Not only that, I assume this would help reduce the load on the main repo going back to your thought of wanting to cull some of the feature branches.
If that sounds good to you, I'd be happy to make a PR inaugurating that section with a link to what I'm intending to maintain.
Thoughts?
The text was updated successfully, but these errors were encountered:
Hi @ctrlplusb, a question rather than an issue. As I was customizing a branch in my fork for my current needs, I realized that some other folks might have done similar things before, while others might have similar requirements.
So, that made me wonder if we should add a section to the Feature Branches page to have a section for 'Community maintained feature branches'?
Folks like me could add our feature branches that we intend to maintain with a short description on there and that would make it easy to circulate ideas.
Not only that, I assume this would help reduce the load on the main repo going back to your thought of wanting to cull some of the feature branches.
If that sounds good to you, I'd be happy to make a PR inaugurating that section with a link to what I'm intending to maintain.
Thoughts?
The text was updated successfully, but these errors were encountered: