hound VS Gitlab CI

The same algorithm is also used in Hound (https://github.com/hound-search/hound) though I have to say the best implementation of code search by far that I've seen is https://grep.app

You really should check it out if you haven't already. It's incredibly useful; I used it all the time. Not open source though.

There is also Hound [8].

[8]: https://github.com/hound-search/hound

Agreed, I already have Hound setup to search across all the different repos I pull from (bitbucket, gh, gitlab, gitea etc) but now I need to find a docker equivalent.

i know you're looking for first-party tools that is part of the whole package, but hound does this fantastically and is extremely easy to setup, and is ridiculously fast.

Especially if this is long term, this is a great tool:

https://github.com/hound-search/hound#hound

It would be great if someone integrated this with tree-sitter plus something to make the search semantics a bit smarter about usages of X:

https://www.etsy.com/codeascraft/announcing-hound-a-lightnin...

Screenshots:

https://jaxenter.com/hound-go-react-code-search-engine-15008...

Another trick I use for Java: javap all the Enums out of the compiled artifacts; these indicate weird things like "modes" that you can use to start asking questions relevant to the domain. Like "why are there four ways to reprice an invoice" or finding the "types" of fees or w/e in a billing system. (assuming enum classes are used)

Nice too that it's a compiled language, so you get the end tool in a nice static binary. As a non-Node dev, I hate the experience of hacking on some project and having to install a giant pool of NPM stuff just run some minifier or linter. Hound is an example of this— the guts of the project are golang, but it has a frontend that uses webpack, jest, etc: https://github.com/hound-search/hound

Which is fine, I guess; definitely use the right tool for the job. And maybe Node developers hate finding my Python projects and needing to set up a virtualenv to run them in. But all the same, I approve a direction where more of this kind of tooling is available without a build-time Node dependency.

[2] https://about.sourcegraph.com/

[3] https://oracle.github.io/opengrok/

[4] https://github.com/hound-search/hound

## https://github.com/gitlabhq/gitlabhq/issues/694

// https://github.com/gitlabhq/gitlabhq/blob/e6d048d769240760008f0dbb6b811e1ebc675292/app/assets/javascripts/ide/components/repo_tab.vue#L3 import { GlIcon, GlTab } from '@gitlab/ui'; import { mapActions, mapGetters } from 'vuex'; import { __, sprintf } from '~/locale'; import ChangedFileIcon from '~/vue_shared/components/changed_file_icon.vue'; import FileIcon from '~/vue_shared/components/file_icon.vue'; import FileStatusIcon from './repo_file_status_icon.vue'; export default { components: { FileStatusIcon, FileIcon, GlIcon, ChangedFileIcon, GlTab, }, props: { tab: { type: Object, required: true, }, }, data() { return { tabMouseOver: false, }; }, computed: { ...mapGetters(['getUrlForPath']), closeLabel() { if (this.fileHasChanged) { return sprintf(__('%{tabname} changed'), { tabname: this.tab.name }); } return sprintf(__('Close %{tabname}'), { tabname: this.tab.name }); }, showChangedIcon() { if (this.tab.pending) return true; return this.fileHasChanged ? !this.tabMouseOver : false; }, fileHasChanged() { return this.tab.changed || this.tab.tempFile || this.tab.staged || this.tab.deleted; }, }, methods: { ...mapActions(['closeFile', 'updateDelayViewerUpdated', 'openPendingTab']), clickFile(tab) { if (tab.active) return; this.updateDelayViewerUpdated(true); if (tab.pending) { this.openPendingTab({ file: tab, keyPrefix: tab.staged ? 'staged' : 'unstaged' }); } else { this.$router.push(this.getUrlForPath(tab.path)); } }, mouseOverTab() { if (this.fileHasChanged) { this.tabMouseOver = true; } }, mouseOutTab() { if (this.fileHasChanged) { this.tabMouseOver = false; } }, }, };

In setting this up, I have followed the gitlab setup guide and the passenger documentation.

Do you know G2 awards 4.4 stars to both GitLab & CircleCI? Just like GitHub stars, StackShares stack counts reflect the popularity of technology. CircleCI boasts around 7.4k stacks, while GitLab enjoys 31.1k stacks. Besides, GitLab as well as GitLab CI are open-source technologies and have garnered 22k+ stars on GitHub. Wait, this is not a reflection of how good GitLab is at CI/CD. These numbers reflect overall popularity. CircleCI is primarily “a niche-focused continuous integration tool” while GitLab wears multiple hats, including “version control & code collaborator.”