Search results
CodePilot.ai: The code search application designed for developers, by developers. Find faster, better solutions from GitHub, Stack Overflow, private code bases, custom data sources, and anywhere else code lives. Get answers at your fingertips, so you can focus on what really matters.
People also ask
What is codepilot?
What happened to codepilot AI?
What is codepilot GitHub - codepilotai/codepilot?
Does codepilot have public members?
CodePilot.ai is going Open Source! After 2 years of work, 36 releases, 23,000+ installs and more queries than we can count we are happy to report that we are Open Sourcing CodePilot.ai. You will have more options and flexibility, also more privacy.
- CodePilot.ai
- Production Configuration
- Development
- Folder Architecture
- Filenames
- HTML
- JavaScript
- Styles
- Images, fonts, and other miscellaneous files
- Themes
This and others READMEs in the repo serve as living documents and the source of truth for our development practices.
•Design
•Split Testing
•Unit Testing
•End to End testing
•Services
To configure this app for production, add production keys for all services in services.config.js.
Commits Features
To ensure frequent communication, all features will be done in feature branches (we can even disable pushing to master). Here's a good process for starting a new feature:
PR Updates
If you're reviewing a PR and want to make some updates yourself before merging, make sure: 1.You communicate with whoever owns the PR and receive their explicit consent before making changes. Otherwise, they might also make changes and accidentally overwrite your work. 2.This isn't a change the owner of the PR could be guided to make themselves and would learn from. On a team with remote members, PRs are a great opportunity to share expertise, but "just taking over" will lead to siloed knowledge and slower development in the long run.
PR Merging
GitHub has several ways for us to merge PRs: •Rebase & merge: Preferred for most PRs, with meaningful commits that tell a story and always have the app in a working condition. •Squash & merge: Preferred for bugfix PRs, which will often only have one commit, or multiple meaningless commits, such as: fix bug, fixes #123, ok, really fixed bug now, bug even fixed on windows, etc. Also preferred for PRs that have gone through a lot of iteration/troubleshooting, where the app is not always in a working condition.
•.electron-vue: Contains the dev server and build config, which should rarely need to be modified. Changes to these files should be made with caution, since they greatly affect everyone's dev experience.
•build: Includes assets used during build.
•src: Manually edited files should be in here 99% of the time. Any files that go through the build system will be in here.
•split-tests: Where we initialize A/B tests. These randomly chosen value for each test is automatically added a property for all telemetry.
•main: Electron-specific code, where our app is initialized and the main window is created.
•renderer: Mostly Vue-specific code to render the frontend.
One note about files: always use kebab-case in filenames, unless the file requires otherwise or is documentation (GitHub treats README.md files differently than other files).
Using any uppercase letters can cause issues with Git on case-insensitive filesystems.
In the of a .vue file
This will be the case for ~95% of HTML. What you're writing is "normal" HTML, but since Vue has a chance to parse it before the browser does, we can do a few extra things that normally aren't possible in a browser. For example, any element or component can be self-closing: The above simply compiles to: This feature is especially useful when writing components with long names, but no content:
In a render function
Render functions are alternatives to templates. Components using render functions will be relatively rare, written only when we need either: •the full expressive power of JavaScript, or •better rendering performance through stateless, functional components These components can optionally be written using an HTML-like syntax within JavaScript called JSX.
Conventions
These conventions are always open to discussion, should be adhered to unless there's a compelling reason not too.
The JavaScript we use is compiled by stage 0 Babel, by way of Webpack. Configuration for Babel is in the .babelrc.js file at the root of this project and configurations for Webpack are in the .electron-vue folder, also at the root.
Babel allows us to write more modern JavaScript without having to worry about what's supported by Node/Chromium. If you're (relatively) new to features such as const, let, and => (arrow functions), take some time to read about the following features in Babel's ES2015 guide:
•Arrow functions
•Template literals
•Destructuring
•Spread operator
TailwindCSS
The application makes heavy use of TailwindCSS as our CSS framework of choice. The main difference compared to typical CSS frameworks like Bootstrap is that it’s an utility-first framework that doesn’t come with any predefined component styles. Instead it provides hundreds of utility classes that can be composed together to create components. For example: The values used by TailwindCSS depend on the configuration that can be found in src/renderer/tailwind.js. Changes to the configuration will affect the whole application. Through the usage of TailwindCCS, we rely on the framework to keep the visual harmony in our app. For example, by keeping the paddings, margins and colors the same across the whole application.
Handwritten CSS
If something can’t be solved with a combination of TailwindCSS utility classes we fallback to writing our own CSS rules. This this, we use the SCSS modules, which you can activate by adding the lang="scss" and module attributes to style tags in Vue components. Otherwise, the tag is assumed to just contain normal CSS.
SCSS
SCSS is just a superset of CSS, meaning any valid CSS is also valid SCSS. This allows you to easily copy properties from other sources, very much in the CodePilot.ai spirit. 😄 It also means you can stick to writing the CSS you're still comfortable with while you're learning to use more advanced SCSS features. I specifically recommend reading about: •Variables •Nesting •Operators Those are the features you'll use 99% of the time.
Importing assets in JavaScript Referencing assets in CSS
To access the @assets alias from CSS, you have to use the ~ prefix:
Referencing assets in HTML
The ~ prefix is also necessary in HTML:
Checklist for working on themes
1.Add variables to all themes found in src/themes. "variable-name" : value
2.Add variable in branding.scss $variable-name: var(--variable-name)
3.Test changes in all themes.
GPT Pilot is the core technology for the Pythagora VS Code extension that aims to provide the first real AI developer companion. Not just an autocomplete or a helper for PR messages but rather a real AI developer that can write full features, debug them, talk to you about issues, ask for review, etc.
Mar 30, 2023 · Oege De Moor and his team at GitHub collaborated with OpenAI to bring the first at scale example of using LLMs for development, specifically OpenAI's codex model. Copilot offers real-time hints for the code you are writing by providing suggestions as "ghost text" based on the context of the surrounding code.
- 1.91
CodePilot.ai has 3 repositories available. Follow their code on GitHub.
Sep 26, 2023 · Codepilot is your new programming buddy and is basically GitHub Copilot on Steroids. It’s an expert on your projects codebase. It leverages Vectra, my local Vector DB, to maintain an index of your projects code that gets checked in right alongside the rest of your code. You’ll need an OpenAI key but that’s it.
