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

[CHA-403] Private messaging #1452

Merged
merged 3 commits into from
Jan 28, 2025

Conversation

totalimmersion
Copy link
Contributor

This PR is adding private messaging for a select list of users in a channel. If the user who sends the message has the CreateRestrictedVisibilityMessage permission, then by adding `restricted_visibility: [ 'john', 'jane' ] would limit the visibility of that message to only john and jane. The other members of the channel can't see the message. The sender of the message can always see it.

Copy link
Contributor

github-actions bot commented Jan 28, 2025

Size Change: 0 B

Total Size: 467 kB

ℹ️ View Unchanged
Filename Size
dist/browser.es.js 102 kB
dist/browser.full-bundle.min.js 57.4 kB
dist/browser.js 103 kB
dist/index.es.js 102 kB
dist/index.js 103 kB

compressed-size-action

@@ -15,8 +15,5 @@ jobs:

- uses: ./.github/actions/setup-node

- name: Commit message lint
run: echo "${{ github.event.pull_request.title }}" | yarn commitlinter
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of removing the linter we could use FIXES CHA-403 and maintain the rules for commit description.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Following those rules would help us in the future using automated release with tools like semantic-release

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

of course we could, but what is the purpose? all these commits gets squashed anyways.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand this lints the PR title that is later used when squash merging the PR. Or does it do sth different?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's linting individual commits as well within the branch/pr.

@totalimmersion totalimmersion merged commit b9c778d into master Jan 28, 2025
5 checks passed
@totalimmersion totalimmersion deleted the feature/cha-398_restricted_message_visibility branch January 28, 2025 16:06
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.

3 participants