Not planned
Description
There are 2 repositories which collect issues available for contributors:
- https://github.com/ubiquity/devpool-directory: Public repo, any contributor can take issue there
- https://github.com/ubiquity/devpool-directory-private: Private repo, only core contributors can take issues there since that repo issues may contain sensitive/NDA data
The issue is that we somehow need to sync code changes between https://github.com/ubiquity/devpool-directory and https://github.com/ubiquity/devpool-directory-private. We can't simply fork https://github.com/ubiquity/devpool-directory-private from https://github.com/ubiquity/devpool-directory and use github UI since private repos can't be synced.
What should be done:
- when a new code change is introduced in https://github.com/ubiquity/devpool-directory then this code change should also appear in https://github.com/ubiquity/devpool-directory-private
Possible solution described here
Activity
jordan-ae commentedon May 26, 2024
@rndquu This up for grabs?
rndquu commentedon May 27, 2024
Yes, you may setup code sync between https://github.com/ubiquity/devpool-directory and your forked instance of https://github.com/rndquu/devpool-directory-private-test for testing purposes and open a PR, I will check how it works with https://github.com/ubiquity/devpool-directory-private then
jordan-ae commentedon May 28, 2024
/start
ubiquibot commentedon May 28, 2024
Tips:
/wallet 0x0000...0000
if you want to update your registered payment wallet address.ubiquibot commentedon Jun 4, 2024
# These linked pull requests are closed: <a href="https://github.com/ubiquity/devpool-directory/pull/1193">#1193</a>
rfc.ubq.fi
) ubiquity/work.ubq.fi#54work.ubq.fi
ubiquity/.github#115ubiquity/devpool-directory
andubiquity/devpool-directory-private
ubiquity/devpool-directory#14009 remaining items