Custom Fields - remove early access marker from incident custom fields pages #701
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
imjaroiswebdev
requested changes
Jun 15, 2023
There was a problem hiding this comment.
@jedelson-pagerduty thank you for the quick response to remove the markers on docs. However, before moving forward with the merge, heimweh/go-pagerduty#134 was merged and therefore You would need to update the go-pagerduty dependency in this same PR please.
jedelson-pagerduty
force-pushed
the
issue/custom-fields-ga
branch
from
2bc23db to
1d994c9
Compare
|
@imjaroiswebdev should be all set now. |
imjaroiswebdev
approved these changes
Jun 16, 2023
…marker from incident custom fields pages
jedelson-pagerduty
force-pushed
the
issue/custom-fields-ga
branch
from
1d994c9 to
51a6508
Compare
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.
Incorporates heimweh/go-pagerduty#134
as well as updating the documentation pages now that Custom Fields is Generally Available