base_requirements.txt can now be kept directly in sync with the cicnet/cic repo, as the proxy (and down the line maybe other things) are not relevant for the higher-level cic context.
`base_requirements.txt` can now be kept directly in sync with the `cicnet/cic` repo, as the proxy (and down the line maybe other things) are not relevant for the higher-level cic context.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
base_requirements.txtcan now be kept directly in sync with thecicnet/cicrepo, as the proxy (and down the line maybe other things) are not relevant for the higher-level cic context.Sounds good. Maybe we can remove the proxy deployment command from the script entirely?
@kamikazechaser can we merge this?