This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Add Security.txt feature attribution to community member #7659
Conversation
This file contains hidden or 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
jeff-matthews
added
Editorial
dobooth
approved these changes
Aug 3, 2020
|
Hi @jeff-matthews, thank you for your contribution! |
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Purpose of this pull request
This pull request (PR) adds a note attributing the security.txt feature to the community member kalpmehta who contributed it to the Magento 2 code base.
A previous PR (#7615) attributed the new devdocs topic to the community member, but the community member also contributed the code. I confirmed with Magento Community Engineering.
We've recognized code contributions like this no devdocs before. See Google reCAPTCHA for an example.
Affected DevDocs pages
Links to Magento source code