RUM-10224: Add octo sts policy for read access#2741
Merged
aleksandr-gringauz merged 1 commit intoJun 19, 2025
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #2741 +/- ##
===========================================
- Coverage 69.77% 69.75% -0.01%
===========================================
Files 824 824
Lines 30790 30790
Branches 5177 5177
===========================================
- Hits 21481 21477 -4
- Misses 7844 7850 +6
+ Partials 1465 1463 -2 🚀 New features to boost your workflow:
|
aleksandr-gringauz
force-pushed
the
aleksandr-gringauz/RUM-10224/add-octo-sts-policy-for-read-access
branch
4 times, most recently
from
June 19, 2025 11:25
8033404 to
c143400
Compare
Base automatically changed from
aleksandr-gringauz/RUM-10224/add-dd-octo-sts-to-dockerfile
to
develop
June 19, 2025 11:27
aleksandr-gringauz
force-pushed
the
aleksandr-gringauz/RUM-10224/add-octo-sts-policy-for-read-access
branch
6 times, most recently
from
June 19, 2025 11:43
164f674 to
90fe462
Compare
aleksandr-gringauz
force-pushed
the
aleksandr-gringauz/RUM-10224/add-octo-sts-policy-for-read-access
branch
from
June 19, 2025 11:44
90fe462 to
96e067d
Compare
aleksandr-gringauz
marked this pull request as ready for review
June 19, 2025 11:45
0xnm
approved these changes
Jun 19, 2025
mariusc83
approved these changes
Jun 19, 2025
aleksandr-gringauz
deleted the
aleksandr-gringauz/RUM-10224/add-octo-sts-policy-for-read-access
branch
June 19, 2025 12:09
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
What does this PR do?
This policy is for GitLab CI in
dd-sdk-androidto be able to access release info about our own repo (for this).Docs for dd-octo-sts.
I am following this example, but putting
*so that any branch could access.For creating PRs in shopist and mobile app I plan to create policies in their repos.
I will start actually using
dd-octo-stsforcheck-release-pipelinein the next pr, because the policy yamls only from default branches are checked (link). And our default branch isdevelop.I have no idea if this file works and there is no way to test.
I'll have to test after merging.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)