update my fork 22/09/2020 #2
Merged
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
[Update] Merging Master to Canary
[HTP-0000] Update Canary
Rubicon: Migrating Adapter + new version
[HTP-0001] TrustX Adapter: migrate in new repo
BRealTime, Beachfront, LockerDome: Merge up from master into canary
Moving Optimera to new repo.
Removed Rubicon From Canary
Merge up from master to canary
Master into Canary
Rubicon Adapter new version 2.1.4
…-library-adapters into feature/aol-adapter
enable ccpa and tcf2.0
add 33across adapter
Add entry to changelog file.
…-library-adapters into feature/aol-adapter
…-library-adapters into feature/aol-adapter
…-library-adapters into feature/aol-adapter
…-library-adapters into feature/aol-adapter
…-library-adapters into feature/aol-adapter
…-library-adapters into feature/aol-adapter
…-signals-for-ccpa [HTP-127] Sharethrough: Consume CCPA privacy signals
[HTP-132] 33Across Adapter: New Certification
updated the links
DOCUMENTATION UPDATES -Updated "master branch" description under Introduction. Removed the part that stated all new certified adapters should merge against this (with library process changes, they should now merge against canary). -Updated "canary branch" description under Introduction. With library process changes, the canary branch will not be for "already-certified adapters", it will be part of the certification process as well. -Updated New Adapters section under Introduction. With process changes, they must first merge to canary for testing, and then merge to master. -Updated Code Submission Guidelines section to include the two code submission checklists for bidding and non-bidding adapters from KB (https://kb.indexexchange.com/ix_library_partners/build_adapter/code_submission_checklist_for_bidding_adapters.htm)
Update README.md
Promote TrustX CCPA Update From Canary to Production
Promote AOL Port from canary to production
Update appnexus endpoint
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Type of Change
Description of Change
Related Issue