forked from mattermost/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Configure WhiteSource Bolt for GitHub #1
Open
mend-bolt-for-github
wants to merge
1
commit into
master
Choose a base branch
from
whitesource/configure
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rutam21
pushed a commit
that referenced
this pull request
Feb 19, 2022
* Update conf.py * Update open-source-components.rst * Update release-lifecycle.rst * Reliable Websockets: default to true Documentation for: mattermost/mattermost#17890 Updated: - Set Up, Manage, Onboard, and Comply > Set Up Mattermost > Self-Managed Deployments > Configuration Settings > Experimental Settings only in config.json > Enable Reliable Websockets - Updated the default value of the config setting to ``true`` * PR didn't follow internal processes for submission * Re-added file deleted in error * Re-added the correct file that was deleted in error * MM-36779 - Add ChimeraOAuthProxyURL config option (mattermost#4928) * MM-36779 - Add ChimeraOAuthProxyURL config option Documentation for: mattermost/mattermost#17888 Updated: - Set Up, Manage, Onboard, and Comply > Set Up Mattermost > Self-Managed Deployments > Configuration Settings > Plugins (Beta) - Added the Chimera OAuth Proxy URL configuration setting * Added ChimeraOAuthProxyUrl to Telemetry * added note about the setting being available only via config.json * Update source/configure/configuration-settings.rst Co-authored-by: Justine Geffen <[email protected]> * Update source/configure/configuration-settings.rst Co-authored-by: Justine Geffen <[email protected]> Co-authored-by: Justine Geffen <[email protected]> * Reliable Websockets: default to true (mattermost#4918) Documentation for: mattermost/mattermost#17890 Updated: - Set Up, Manage, Onboard, and Comply > Set Up Mattermost > Self-Managed Deployments > Configuration Settings > Experimental Settings only in config.json > Enable Reliable Websockets - Updated the default value of the config setting to ``true`` * Added functionality to archive/unarchive teams from system console (mattermost#4927) * Added functionality to archive/unarchive teams from system console Documentation for: mattermost/mattermost-webapp#8129 Updated: - Set Up, Manage, Onboard, and Comply > Manage Mattermost > Self-Managed Deployments > Managing Team and Channel Members (E20) > Team Profile - Updated section to include details on how to archive/unarchive the team * Added archive/unarchive updates to Cloud-specific page * Updated LHS - Moved self-managed topic from all instances to self-managed - Added Cloud-specific topic * added mmctl equivalent for team restore * added mmctl equivalent for team restore (self-managed) * Update source/manage/cloud-team-and-channel.rst Co-authored-by: Justine Geffen <[email protected]> * Update source/manage/team-channel-members.rst Co-authored-by: Justine Geffen <[email protected]> * Update data-retention-policy.rst (mattermost#4937) * Update data-retention-policy.rst Adding docs for custom data retention policies. * Update data-retention-policy.rst * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update data-retention-policy.rst * Update data-retention-policy.rst * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update source/comply/data-retention-policy.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]> Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update important-upgrade-notes.rst (mattermost#4811) * Update important-upgrade-notes.rst * Update important-upgrade-notes.rst * Update important-upgrade-notes.rst * Fix typos * MM-36547 Renamed 'Mute Channel' and 'Edit Channel Header' menus (mattermost#4941) Documentation for: mattermost/mattermost-webapp#8313 Updated: - Messaging > Manage Teams, Channels, and Members > Managing Channels > Creating a Direct or Group Message - Updated section to include mute, unmute, and edit header options for group and direct messages * MM-35722: CRT, post click open thread (mattermost#4942) Documentation for: mattermost/mattermost-webapp#8342 Updated: - Messages > Work with Messages > Organizing Conversations using Collapsed Reply Threads (Beta) > Start or Reply to Threads - Updated Tip bullet point #1 to clarify that uses can click anywhere in a message in the center pane to view it/reply to it * MM-35470 Disable config watching logic (mattermost#4951) * MM-35470 Disable config watching logic Documentation for: mattermost/mattermost#17913 Updated: - Set Up, Manage, Onboard, and Comply > Set Up Mattermost > Self-Managed Deployments > Configuration Settings - Updated introductory content to remove < v5.12 legacy note and add config watcher note and link to mmctl command * Update source/configure/configuration-settings.rst Co-authored-by: Justine Geffen <[email protected]> * v5.38.0 Changelog (mattermost#4810) * Update self-managed-changelog.md * Update self-managed-changelog.md * Update self-managed-changelog.md * Update self-managed-changelog.md * Update self-managed-changelog.md * Update self-managed-changelog.md * Update self-managed-changelog.md * Apply suggestions from code review Co-authored-by: Carrie Warner (Mattermost) <[email protected]> * Update self-managed-changelog.md * Update self-managed-changelog.md * Update self-managed-changelog.md Co-authored-by: Carrie Warner (Mattermost) <[email protected]> Co-authored-by: Amy Blais <[email protected]> Co-authored-by: Justine Geffen <[email protected]> Co-authored-by: Katie Wiersgalla <[email protected]>
Rutam21
pushed a commit
that referenced
this pull request
Feb 19, 2022
* CRT updates re server perf * Update organizing-conversations.rst * Update organizing-conversations.rst * Update source/messaging/organizing-conversations.rst * Update source/configure/configuration-settings.rst * Update source/configure/configuration-settings.rst * Update source/configure/configuration-settings.rst Co-authored-by: Carrie Warner (Mattermost) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Welcome to WhiteSource Bolt for GitHub! This is an onboarding PR to help you understand and configure settings before WhiteSource starts scanning your repository for security vulnerabilities.
🚦 WhiteSource Bolt for GitHub will start scanning your repository only once you merge this Pull Request. To disable WhiteSource Bolt for GitHub, simply close this Pull Request.
What to Expect
This PR contains a '.whitesource' configuration file which can be customized to your needs. If no changes were applied to this file, WhiteSource Bolt for GitHub will use the default configuration.
Before merging this PR, Make sure the Issues tab is enabled. Once you merge this PR, WhiteSource Bolt for GitHub will scan your repository and create a GitHub Issue for every vulnerability detected in your repository.
If you do not want a GitHub Issue to be created for each detected vulnerability, you can edit the '.whitesource' file and set the 'minSeverityLevel' parameter to 'NONE'.
❓ Got questions? Check out WhiteSource Bolt for GitHub docs.
If you need any further assistance then you can also request help here.