Skip to content
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

Add read-only permission for organizations and dynamic token check at current block #4

Closed

Conversation

jjranalli
Copy link

@jjranalli jjranalli commented Apr 13, 2022

Read Only

When giving access to repos owned by an organisation, new members get "write" access by default. This may be undesirable.

  • Added read-only option during gate creation (only shows up if repo is owned by an org)
  • Added readOnly to Gate in db schema
  • Added frontend elements related to read-only option
  • Changed .env.sample and readme
  • Fixed links that were hardcoded to 'gaterepo.com'

Dynamic Check

Checking number of tokens held dynamically and not at a specific block might be desirable in some scenarios. For example, it avoids having to periodically create new links to allow new holders to get access to the repo.

  • Added Dynamic check option during gate creation
  • Added required logic in api/gates endpoints
  • Added dynamicCheck to Gate in db schema + added default values to both dynamicCheck and readOnly proposed in Add read-only option for organization-owned repos #3 (should prevent issues during db migration)
  • Added frontend elements related to dynamic check option

Btw great work doing this ❤️

@jjranalli jjranalli changed the title Add option to check tokens owned at current block Add read-only permission for organizations and dynamic token check at current block Apr 13, 2022
@jjranalli jjranalli closed this May 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant