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

[DOC] Add Docs for Constant Keyword Field #6696

Open
1 of 4 tasks
hasnain2808 opened this issue Mar 15, 2024 · 5 comments
Open
1 of 4 tasks

[DOC] Add Docs for Constant Keyword Field #6696

hasnain2808 opened this issue Mar 15, 2024 · 5 comments
Assignees
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR.

Comments

@hasnain2808
Copy link

hasnain2808 commented Mar 15, 2024

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
Pull Request -> opensearch-project/OpenSearch#12285

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
Issue -> opensearch-project/OpenSearch#9981

@hdhalter hdhalter added 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed untriaged labels Mar 15, 2024
@hdhalter
Copy link
Contributor

Thanks, @hasnain2808 ! Would you like to contribute the documentation for this feature? See https://github.com/opensearch-project/documentation-website/blob/main/CONTRIBUTING.md#contributing-content.

@hasnain2808
Copy link
Author

@hdhalter
I would like to try this out but it might take some time. Is there some deadline we track with regards to merging the actual pr?

@hdhalter
Copy link
Contributor

@hdhalter I would like to try this out but it might take some time. Is there some deadline we track with regards to merging the actual pr?

That would be great! Since this is not tied to a release, there is no deadline to merge. PRs go through our internal review review process, so it might take some time before we can merge anyway.

@hasnain2808
Copy link
Author

@hdhalter
Is there a requirement for the documentation pr to be ready for the code pr to be merged?

@hdhalter
Copy link
Contributor

@hdhalter Is there a requirement for the documentation pr to be ready for the code pr to be merged?

Not at this time. But we are talking about implementing something that restricts a PR from being merged unless a doc PR is up and in review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog - DEV Developer assigned to issue is responsible for creating PR.
Projects
None yet
Development

No branches or pull requests

2 participants