-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename or recreate the repo #1
Comments
New uninitialized repository created here; https://github.com/bcgov/aries-cloudagent-python |
Over to @nrempel |
All issues have been transferred to the new repo, and the |
TelegramSam
referenced
this issue
in TelegramSam/aries-cloudagent-python
Jul 10, 2019
requires routing?
andrewwhitehead
pushed a commit
that referenced
this issue
Oct 10, 2019
Sync with master after rich admin api text update
andrewwhitehead
pushed a commit
that referenced
this issue
Nov 6, 2019
Merge with upstream refactoring
olichwiruk
added a commit
to olichwiruk/aries-cloudagent-python
that referenced
this issue
May 25, 2020
Extend for development
andrewwhitehead
pushed a commit
that referenced
this issue
Jun 22, 2020
Merge master from hyperledger repo
ianco
pushed a commit
that referenced
this issue
Apr 24, 2021
Taking latest changes done till EOD - 24/4/21
ianco
pushed a commit
that referenced
this issue
Nov 29, 2021
Fix faber demo to run in multi-ledger mode
This was referenced Mar 10, 2022
swcurran
pushed a commit
that referenced
this issue
Nov 8, 2022
Signed-off-by: Daniel Bluhm <[email protected]>
thiagoromanos
pushed a commit
to CPqD/aries-cloudagent-python-cpqd
that referenced
this issue
Jul 2, 2024
Authored-by: Antonio Mateus de Sousa <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please at least rename this repo to "aries-cloudagent-python" in preparation for transferring it to Hyperledger. Alternatively create a new repo by that name. Either way, please make sure that the standard BC Gov files are put into the repo - licence, contributions, etc. All repos should always have that, and Shea mentioned there might be a tool for doing that.
@nrempel - should we just create a new repo, or use this one? Remember that we want the commit history on the files.
Thanks!
The text was updated successfully, but these errors were encountered: