Skip to content

Conversation

@Calvinaud
Copy link
Contributor

@Calvinaud Calvinaud commented Nov 25, 2025

Proposed changes

Create a new role Editor: 5339

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

  • New feature (non-breaking change which adds functionality)
  • Bugfix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING doc
  • I have signed the commit for DCO to be passed.
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have added necessary documentation (if appropriate)

Dependency

  • Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

Signed-off-by: Calvin Audier <[email protected]>
- Update graphql scheme to add new role
- Update role to include Editor role

Signed-off-by: Calvin Audier <[email protected]>
- Add Executor in list of role
- Update view to select new role during invite
- Update view to view new role on members status

Signed-off-by: Calvin Audier <[email protected]>
- Update use permission to include check for editor
- Update button to change some from OWNER to EDITOR

Signed-off-by: Calvin Audier <[email protected]>
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.

1 participant