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

Move license to root for github detection #144

Merged
merged 4 commits into from
Oct 7, 2021

Conversation

earmenda
Copy link
Contributor

@earmenda earmenda commented Oct 7, 2021

Closes #139

Code Changes

  • Move LICENSE file to root directory

Steps to Confirm

Was not able to confirm other than running licensee to verify our license can be identified correctly:

eduardoarmendariz@eth-27s-mbp fides % licensee
License:        NOASSERTION
Matched files:  LICENSE, README.md
LICENSE:
  Content hash:  bec905d850e7f5dc2e2db78a950d4a9db560a0b8
  Confidence:    100.00%
  Matcher:       Licensee::Matchers::Exact
  License:       Apache-2.0
README.md:
  Content hash:  8da4fea4d51b54efdd898b75fe7bd8c3a7a436f0
  License:       NOASSERTION
  Closest non-matching licenses:
    0BSD similarity:   4.84%
    WTFPL similarity:  4.58%
    ISC similarity:    3.97%

Pre-Merge Checklist

  • All CI Pipelines Succeeded
  • Documentation Updated

Description Of Changes

  • Im not sure how to confirm if this will work, I've tried a few things and don't see the license appear in the home page

@ThomasLaPiana
Copy link
Contributor

@earmenda i used the license generator in GitHub and it still isn't detecting, I think we just need to merge it to main for this to work. going to go ahead and do so

LICENSE Outdated Show resolved Hide resolved
@ThomasLaPiana ThomasLaPiana merged commit 4e389e2 into main Oct 7, 2021
@ThomasLaPiana ThomasLaPiana deleted the earmenda-fix-license-github branch October 7, 2021 16:47
ThomasLaPiana pushed a commit that referenced this pull request Aug 17, 2022
* Log just potentially affected fields on the execution logs, rather than all of the fields.

* Add test asserting rules with overlapping data categories don't produce duplicate fields in log.

* Update reporting docs to correct an inaccuracy  - queries are not logged in the execution logs, we just have the status of the request and potential fields affected.

- Also have the examples show the in_processing/complete execution logs instead of pending execution logs, because we don't create pending execution logs for an individual collection anymore.
- Privacy requests can also have a "paused" status due to pre-execution policy webhooks

* Add missing backticks around collection names.
ThomasLaPiana pushed a commit that referenced this pull request Sep 26, 2022
* Log just potentially affected fields on the execution logs, rather than all of the fields.

* Add test asserting rules with overlapping data categories don't produce duplicate fields in log.

* Update reporting docs to correct an inaccuracy  - queries are not logged in the execution logs, we just have the status of the request and potential fields affected.

- Also have the examples show the in_processing/complete execution logs instead of pending execution logs, because we don't create pending execution logs for an individual collection anymore.
- Privacy requests can also have a "paused" status due to pre-execution policy webhooks

* Add missing backticks around collection names.
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.

Project license is not displayed in the GitHub UI
3 participants