Contributing guidelines #476
daspecster
started this conversation in
Ideas
Replies: 2 comments
-
Well, I think we inherit most of the generic stuff, but a contributing file for this repo that's specific to us would probably be helpful for things like how to run our tests, common gotchas that are specific to django, etc. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I tried to setup a dev environment by using the given docker-compose.yml file in the repo (running [+] Building 1.8s (4/4) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 32B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> ERROR [internal] load metadata for docker.io/library/django-celery-beat_base:latest 1.7s
=> [auth] library/django-celery-beat_base:pull token for registry-1.docker.io 0.0s
------
> [internal] load metadata for docker.io/library/django-celery-beat_base:latest:
------
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Any suggestions? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
I was looking at the
issue_template.md
file that @liquidpele added recently. Great addition btw!I noticed that we don't have contributing guidelines for this repo.
Do we inherit from the Celery guidelines or should we add our own
CONTRIBUTING.rst/md
file for this repo?Beta Was this translation helpful? Give feedback.
All reactions