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
Do we pull new features from Eliza often? how often? what features? will they be compatible with our repo? Do we need to change our approach to ensure compatibility with Eliza pulls?
Do we build our own RS features and from time to time share some functionality with the Eliza (Open source) community? How to do that in terms of repo compatibility?
Our repo is forked and behind Eliza by a bunch, is it still compatible or did we introduce breaking changes, etc.
Caner Comment -
do we pull new features from Eliza often? how often? what features? will they be compatible with our repo? Do we need to change our approach to ensure compatibility with Eliza pulls?
yes we pull the latest changes from the develop branch to our sa-eliza repo every 5 minutes
Do we build our own RS features and from time to time share some functionality with the Eliza (Open source) community? How to do that in terms of repo compatibility?
that’s correct, depending on the features we decide to share it with the broader community or keep them in sa-eliza, for example coinbase plugin was merged into the upstream repo while github plugins and client are kept within our sa-eliza repo.
Our repo is forked and behind Eliza by a bunch, is it still compatible or did we introduce breaking changes, etc.
nope we are up to date with the upstream repo branches
Okay so the flow is then "feature-specific-branch" get's pull requested into "dev branch" and then "dev branch" after doing QA/testing gets merged into "main" branch for RS. And before a feature-specific-branch is created it should be created off the "dev branch"
what's the relationship between the dev branch and the main branch in the RS repo?
The text was updated successfully, but these errors were encountered:
ArsalonAmini2024
changed the title
RS relationship with Eliza repository
RSP Codebase relationship with Eliza repository
Jan 23, 2025
Hi @monilpat this was something we talked about before. I think you and the devs already discussed this and have a solution in place. Can you comment that solution or document it into GDRIVE and then link it here + close this issue with a comment?
Arsalon Comment -
Caner Comment -
do we pull new features from Eliza often? how often? what features? will they be compatible with our repo? Do we need to change our approach to ensure compatibility with Eliza pulls?
Do we build our own RS features and from time to time share some functionality with the Eliza (Open source) community? How to do that in terms of repo compatibility?
Our repo is forked and behind Eliza by a bunch, is it still compatible or did we introduce breaking changes, etc.
Okay so the flow is then "feature-specific-branch" get's pull requested into "dev branch" and then "dev branch" after doing QA/testing gets merged into "main" branch for RS. And before a feature-specific-branch is created it should be created off the "dev branch"
The text was updated successfully, but these errors were encountered: