今日已更新 35 条资讯 | 累计 37284 条内容
关于我们

标签:#GitHub

找到 1537 篇相关文章

AI 资讯

Cursor Releases Origin as an Agent-Native Alternative to GitHub

AI coding agent Cursor has launched Origin, a git based code hosting platform embedded inside its AI-powered editor, positioning it as an alternative to GitHub for teams that already work in Cursor. Origin is rolling out in early beta on Pro, Teams and Enterprise plans, and lives inside a new Codebase tab within the Cursor application. By Matt Saunders

2026-08-25 原文 →
AI 资讯

A Simple CI/CD Pipeline That Actually Works

The Problem with Most CI/CD Tutorials Most tutorials show you a pipeline that deploys a "hello world" app to a free Heroku instance. They skip the messy parts: secrets, rollbacks, and the moment your pipeline breaks because a dependency changed. I've been there. After years of fighting with over-engineered setups, I settled on a minimal pipeline that's easy to understand, debug, and extend. It's not fancy, but it works. The Core Idea A CI/CD pipeline is just three stages: Test - run automated checks Build - create an artifact Deploy - push the artifact to a server We'll use GitHub Actions because it's free for public repos and integrates with everything. But the same concepts apply to GitLab CI, CircleCI, or Jenkins. The Pipeline File Here's the complete .github/workflows/deploy.yml : name : CI/CD on : push : branches : [ main ] pull_request : branches : [ main ] jobs : test : runs-on : ubuntu-latest steps : - uses : actions/checkout@v4 - uses : actions/setup-node@v4 with : node-version : ' 20' - run : npm ci - run : npm test build-and-deploy : needs : test runs-on : ubuntu-latest if : github.ref == 'refs/heads/main' && github.event_name == 'push' steps : - uses : actions/checkout@v4 - run : npm ci - run : npm run build - name : Deploy to server uses : appleboy/scp-action@v0.1.7 with : host : ${{ secrets.SERVER_HOST }} username : ${{ secrets.SERVER_USER }} key : ${{ secrets.SSH_PRIVATE_KEY }} source : " dist/*" target : " /var/www/myapp" That's it. Let's break it down. Stage 1: Test The test job runs on every push and pull request. It checks out the code, installs dependencies with npm ci (which respects the lockfile), and runs your test suite. If a PR fails tests, the build-and-deploy job won't run because of the needs: test dependency. Stage 2: Build The build-and-deploy job only runs on pushes to main (not on PRs). It builds your app into a dist folder. For a Node.js app, npm run build might be a bundler like Vite or webpack. For a Python app, you'd replace with

2026-08-25 原文 →
开源项目

🔥 AgriciDaniel / claude-obsidian - Self-organizing AI second brain for Obsidian + Claude Code.

GitHub热门项目 | Self-organizing AI second brain for Obsidian + Claude Code. Drop any source and Claude reads, links, and files it into one connected knowledge graph of plain Markdown you own. AI note-taking, personal knowledge management (PKM), and an open-source Notion alternative. Based on Karpathy's LLM Wiki pattern. | Stars: 11,516 | 272 stars today | 语言: Python

2026-08-24 原文 →
AI 资讯

Understanding the Git Workflow:Working directory,staging ,commit and push.

What is Git and Github This is a version control system or tool used to track changes by developers. When one installs git it comes with an inbuilt terminal called gitbash Github is a cloud based platform for storing git repositories online. Just sign up for free,verify via email and your account is created. git and github are connected using a SSH KEY. How Git works. We start by installing git on my Pc, after installation check if git is installed by opening a terminal eg powershell on windows and run git --version Stages Git/Github is broken into four simple stages: working directory is where we write code and amend and delete files. Here changes are made but cannot be tracked unless they are instructed to commit. staging phase is an area where files are modified. commit phase is where git takes everything from the staging area and sends it to our local repository. push phase is where the saved commits are sent to a remote repository like GitHub. Creating folders and files on git bash First identify where we want the folder to be located ls is used to list mkdir "name of the folder" (means make directory) cd " name of the folder" (change directory) Readme texts README.md end with .md since they are written using markdown language.Can use echo,touch or nano commands to write a readme file. If i want to know the contents of my readme file we use: cat README.md git config-this is basically telling it my identity git config --user.name"user" git config --user.email "useremail" git init-this command is used to create or initialize a repository in main/master. git init main git status-shows the repository status. This command shows changes and what is happening in git git status git add-stages changes made git add . this means stage all or one can specify what to be added e.g i want to add only a javascript folder git add script.js git commit-commits records that have been staged in the local git repository.Its like getting a snapshot or memory of the file. git commit -

2026-08-24 原文 →
AI 资讯

From Local Folder to Github: Setting Up my First Project With Git and Github: A Guide

Introduction Managing files locally or manually in your own pc gets out of hand very fast. You might find that you have a file named project_final_1 and project_final_2 which are about the same project but named differently depending on the day the projects were updated or modified. Git Bash is a command line tool that records detailed history of your code as it changes over time GitHub is an online tool where the changes in your code are stored remotely. GitHub does not use folders instead it uses repositories. The repositories make it easier for you to store your work, have a back-up of your work and also showcase your portfolio. Step 1:Installing Git First you have to install git depending on your operating system. Once installed open git bash and you have to tell Git who you are. The code below will help you set up git for the very first time git config --global user.name "put your name here" git config --global user.email "put your email here" After configuration you have to verify your installation with the code below git --version Adding SSH Key For your git to be connected to git hub you have to genarate an ssh key. The key allows your git to access your github without much stress. First you open your terminal or git bash terminal and run the code below to generate the SSH key. ssh-keygen -t ed25519 -C "enter your email here" This code will prompt you on your terminal to save the key on its default location, press enter. Next you will be prompted to enter a passphrase, for easy access and to elimate the chances of forgetting the passphrase you entered just press enter twice. Now you have a public key saved in your pc, use the command below to copy the key. cat ~/.ssh/id_ed25519.pub Adding the Key to GitHub Login into github, click on your profile picture in the top left corner and select settings . in the left navigation bar click SSH and GPG keys . Click the New SSH key button. Give a description of your key (eg .my work laptop), in the drop down menu make

2026-08-23 原文 →
AI 资讯

Understanding The Git Workflow: Working Directory, Staging, Commit and Push

Imagine working on a project for several weeks. You make hundreds of changes across dozens of files. Then your computer crashes. Which version of your project was working yesterday? What did you change? Which changes did your colleague make? And how do you combine everyone's work without overwriting each other's changes? This is where Git comes in. What is Git? Git is an open-source system that enables users to manage their projects, from a single file to large projects. Git is basically a version control system. It provides the necessary resource to help one manage files in the local machine, track the files that have been changed, attach a pointer which marks files which were changed, who did it, and when, and to make it redundant, these files can be pushed into a remote shareable project called repository in Github . Git also has something very key that is called branches . A branch is basically an isolated area of your project where you can work on a copy of the main project without making changes to the main work. Once you are done working on your branch, Git makes it possible to merge all the changes to the main branch. For this article, I will cover these concepts, guiding one on the step by step process of how to do all this. This article assumes that one has Git installed and configured, and has a Github account. We shall also assume that one has a text editor installed, or is conversant with commands in the terminal. We shall cover these concepts in another article. Creating a Project On Your Machine To start, we need to create a folder where we shall be working on our project. On your machine, you can use the good old right click and select New Folder, or, if in terminal, use the command mkdir as follows: mkdir new_project This creates a folder called new_project We shall then open our folder in the terminal, so that we can do the following: Initialize Git Create a file Stage it Commit it Link local repository to remote repository Push to Github account I

2026-08-23 原文 →