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
In compliance with samvera/maintenance#67, Samvera Community repositories should avoid the usage of branches named master.
Further, the standard practices for core components have been to ensure that main tracks the latest stable code contributions. For https://github.com/ActiveTriples/ActiveTriples, these are tracked on development, and as such, I have rebased the new main branch on this fork to track these changes.
Should this project become actively maintained by the Maintenance IG, perhaps deprecating the development branch entirely is possible? I have no strong opinions, but would propose that consistency may be best.
The text was updated successfully, but these errors were encountered:
In compliance with samvera/maintenance#67, Samvera Community repositories should avoid the usage of branches named
master
.Further, the standard practices for core components have been to ensure that
main
tracks the latest stable code contributions. For https://github.com/ActiveTriples/ActiveTriples, these are tracked ondevelopment
, and as such, I have rebased the newmain
branch on this fork to track these changes.Should this project become actively maintained by the Maintenance IG, perhaps deprecating the
development
branch entirely is possible? I have no strong opinions, but would propose that consistency may be best.The text was updated successfully, but these errors were encountered: