Update Nginx ingress controller readme #3014
Closed
Conversation
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
Changed headings to correct markdown syntax
Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.7.0 to 1.7.1. - [Release notes](https://github.com/stretchr/testify/releases) - [Commits](stretchr/testify@v1.7.0...v1.7.1) --- updated-dependencies: - dependency-name: github.com/stretchr/testify dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Markdown tidy up of readme file
To avoid clashes
update to reset main branch and stop files being added to PRs
Bumps [github.com/elastic/package-registry](https://github.com/elastic/package-registry) from 1.7.0 to 1.8.0. - [Release notes](https://github.com/elastic/package-registry/releases) - [Changelog](https://github.com/elastic/package-registry/blob/main/CHANGELOG.md) - [Commits](elastic/package-registry@v1.7.0...v1.8.0) --- updated-dependencies: - dependency-name: github.com/elastic/package-registry dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…com/elastic/package-registry-1.8.0 Bump github.com/elastic/package-registry from 1.7.0 to 1.8.0
…com/stretchr/testify-1.7.1 Bump github.com/stretchr/testify from 1.7.0 to 1.7.1
Bumps [github.com/magefile/mage](https://github.com/magefile/mage) from 1.11.0 to 1.13.0. - [Release notes](https://github.com/magefile/mage/releases) - [Changelog](https://github.com/magefile/mage/blob/master/.goreleaser.yml) - [Commits](magefile/mage@v1.11.0...v1.13.0) --- updated-dependencies: - dependency-name: github.com/magefile/mage dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…com/magefile/mage-1.13.0 Bump github.com/magefile/mage from 1.11.0 to 1.13.0
Bumps [github.com/elastic/elastic-package](https://github.com/elastic/elastic-package) from 0.38.0 to 0.46.0. - [Release notes](https://github.com/elastic/elastic-package/releases) - [Changelog](https://github.com/elastic/elastic-package/blob/main/.goreleaser.yml) - [Commits](elastic/elastic-package@v0.38.0...v0.46.0) --- updated-dependencies: - dependency-name: github.com/elastic/elastic-package dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…com/elastic/elastic-package-0.46.0 Bump github.com/elastic/elastic-package from 0.38.0 to 0.46.0
Tidy up of Markdown in Readme.md, including adding link to developer's documentation, if missing
cherryleaf changed the title 
❕ Build Aborted
Expand to view the summary
Build stats
Steps errors 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
| closing and raising again to fix go.sum error |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 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.
Type of change
What does this PR do?
Tidy up of Markdown in Readme.md, including adding link to developer's documentation, if missing
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots