You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* first pass - support all options via cobra for command line usage
* cleanup, compatability with wrappers
* update changelog
* lint
* update orb
* remove delimiters from orb
* update version string
* length guard
* first pass - move search code to a search package
* clean up the Searcher interface, fix tests
* first pass at support for ripgrep
* update readme
* add homebrew dependency
* native client take 1
* testing stuff
* cleanup
* cleanup docs and options
* more cleanup
* fixes and tests
* move file reading code to a separate... file
* comments
* remove unused code
* simplify hunk consolidation code
* add comment
* refactor some stuff into a separate method
* add more tests
* sort hunks by flag key in tests for stability
* lint
* address review
* fix race in tests
* lint
* don't write to closed channel
* read files concurrently
* fix lint
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,14 +16,19 @@ All notable changes to the ld-find-code-refs program will be documented in this
16
16
```
17
17
- All command line flags can now be specified as environment variables.
18
18
19
+
### Fixed
20
+
21
+
- Exlude negations in `.ldignore` (lines beginning with an exlamation mark) now correctly include files.
22
+
19
23
### Changed
20
24
21
-
- The underlying command line package has been changed for improved ergonomics when configuring options using the command line. Some existing configurations may be invalid, see `ld-find-code-refs --help` for details.
25
+
- The command line tool has been changed for improved ergonomics when configuring options using the command line. Some existing configurations may be invalid, see `ld-find-code-refs --help` for details.
22
26
23
27
### Removed
24
28
25
29
- The `exclude` command-line option has been removed. Use the `.ldignore` file instead.
26
30
- Additional delimiters can no longer be specified using command line flags or environment variables. If you use additional delimiters, or would like to disable delimiters completely, use the YAML configuration described above.
31
+
- `ld_find_code_refs`no longer requires the silver searcher (ag) as a runtime dependency.
Copy file name to clipboardExpand all lines: README.md
+11-26Lines changed: 11 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,30 +29,25 @@ This repository provides solutions for configuring [LaunchDarkly code references
29
29
30
30
We provide turnkey support for common trigger mechanisms and CI / CD providers. You can also invoke the ld-find-code-refs utility from the command line, which can be run in any custom workflow you define (e.g. from a bash script, or a cron job).
| GitLab CI |[Supported](https://docs.launchdarkly.com/integrations/git-code-references/gitlab-ci)|
38
+
| Manually via CLI |[Supported](https://docs.launchdarkly.com/v2.0/docs/custom-configuration-via-cli)|
39
39
40
40
## Execution via CLI
41
41
42
42
The command line program may be run manually, and executed in an environment of your choosing. The program requires your `git` repo to be cloned locally, and the currently checked out branch will be scanned for code references.
43
43
44
-
We recommend ingraining`ld-find-code-refs` into your CI/CD build process. `ld-find-code-refs` should run whenever a commit is pushed to your repository.
44
+
We recommend incorporating`ld-find-code-refs` into your CI/CD build process. `ld-find-code-refs` should run whenever a commit is pushed to your repository.
45
45
46
46
### Prerequisites
47
47
48
-
`ld-find-code-refs`has two dependencies, which need to be installed in the system path:
48
+
`ld-find-code-refs`requires git (tested with version 2.21.0) to be installed on the system path.
**Note**: The underlying dependency used for search, `ag`, has known performance issues when built for Windows. Unofficial Windows builds are available for `ag` from various forks on GitHub, although correctness and performance cannot be guaranteed. If you are experiencing issues running `ld-find-code-refs` on Windows, we recommend using the [Docker image](#docker) instead.
91
-
92
83
A Windows executable of `ld-find-code-refs` is available on the [releases page](https://github.com/launchdarkly/ld-find-code-refs/releases/latest).
93
84
94
-
The following Chocolatey command may be used to install the required dependency, `ag`. If you do not have Chocolatey installed, see `ag`'s documentation for [installation instructions](https://github.com/ggreer/the_silver_searcher#windows).
95
-
96
-
```powershell
97
-
choco install ag
98
-
```
99
-
100
85
#### Docker
101
86
102
87
`ld-find-code-refs` is available as a [docker image](https://hub.docker.com/r/launchdarkly/ld-find-code-refs). The image provides an entrypoint for `ld-find-code-refs`, to which command line arguments may be passed. If using the entrypoint, your git repository to be scanned should be mounted as a volume. Otherwise, you may override the entrypoint and access `ld-find-code-refs` directly from the shell.
@@ -111,7 +96,7 @@ docker run \
111
96
112
97
#### Manual
113
98
114
-
Precompiled binaries for the latest release can be found [here](https://github.com/launchdarkly/ld-find-code-refs/releases/latest). Be sure to install the required [dependencies](#prerequisities) before running `ld-find-code-refs`
99
+
Precompiled binaries for the latest release can be found [here](https://github.com/launchdarkly/ld-find-code-refs/releases/latest). Be sure to install the required [dependencies](#prerequisities) before running `ld-find-code-refs`.
0 commit comments