What do GitHub Actions workflows look like in prod? I'll give you a clue: Branching strategies. One of the benefits of CI/CD is that any code that passes all stages of the development pipeline is automatically pushed to production. To really leverage that benefit however, we implement branching strategies. This is a way of filtering our workflow triggers, only running our them when changes are pushed to specific branches. In this case, it would be the main branch (or whatever branch our production code is on). This allows us to work on new features & bug fixes on separate branches in the background, keeping our application running until our changes are ready, maximising uptime. Have you implemented branching strategies into your work? #devops #git #github #cicd
Siad A.’s Post
More Relevant Posts
-
🚀 Week 4 — Git & GitHub Challenge complete! Spent the week practicing core Git workflows taught by Shubham Bhaiya: forking & cloning, git init → add → commit, branching (git branch / git switch), pushing with a PAT, and even exploring SSH auth as a bonus. Built a week-4-challenge folder, documented every step in solution.md and resolved a merge conflict locally to better understand real-world collaboration. Key takeaways: branching isolates features, enables parallel work, simplifies code review, and reduces risk during merges. 🔗https://lnkd.in/g8zeEX4y #90DaysOfDevOps #GitGithub #DevOps #VersionControl #100DaysOfLearning 🤩
To view or add a comment, sign in
-
Let’s understand 3 commonly used Git commands that every developer should know 👇 🔹 git clone → First-time setup It copies a remote repository (like GitHub) to your local system. 🖥️ Example: git clone https://lnkd.in/ggRei-DU 📦 Think of it as downloading the whole project with its history. 🔹 git fetch → Check for updates It brings the latest changes from the remote repo but doesn’t update your code yet. 👀 You can see what changed before merging. 🔹 git pull → Get & apply updates It’s like fetch + merge — it downloads changes and updates your local branch immediately. 💡 In short: clone → Get repo fetch → See updates pull → Get updates #Git #GitHub #DevOps #CodingLife #SoftwareDevelopment #LearnGit #VersionControl #Developers
To view or add a comment, sign in
-
-
git stash vs git stash pop Ever been halfway through some changes and suddenly had to switch branches? Here’s a simple breakdown 👇 git stash → Safely stores your unfinished work git stash pop → Restores that work back when you’re ready 🔄 Perfect for quick context switching without losing progress. #DevOps #GitHub
To view or add a comment, sign in
-
-
Version Control Best Practices 1. Commit often – Save your progress frequently. 2. Write clear messages – Explain what changed and why. 3. Use branches – Keep new features separate until ready to merge. Good version control makes teamwork easy and your code history clean! #openstage #git #github #learn
To view or add a comment, sign in
-
-
🔧 Git Cleanup Task Completed — Keeping the Repository Clean & Reliable! Today, I worked on a scenario where the Nautilus application development team mistakenly created a few unwanted files in the /usr/src/kodekloudrepos/news repository on the Storage server. The requirement was simple but important: ✔️ Clean the repository ✔️ Do not add or push any new files ✔️ Ensure git status shows a clean working tree To fix this, I reverted the working directory back to its last committed state, ensuring no accidental files remained. This helped restore a clean and stable environment for the developers to continue their work safely. 🧹 Result: The repo is now fully clean — no untracked files, no pending changes, and git status is perfectly green. Small tasks like these play a major role in maintaining code quality and collaborative efficiency. 🚀 #DevOps #Git #VersionControl #KodeKloudEngineer #LearningByDoing #DevOpsJourney #100DaysOfDevOps
To view or add a comment, sign in
-
Git & GitHub Q&A…. To help you strengthen your fundamentals. • Practical definitions • Common commands • Branching, merging & rebasing • Handling conflicts • Stash, tags, workflows • GitHub Actions basics If you’re in the DevOps journey, this is exactly the layer of knowledge interviewers quietly evaluate. #cicd #Salesforcedevops #git #github #vscode
To view or add a comment, sign in
-
In real-time projects, Git is our best friend — but sometimes it becomes a puzzle! Here are some common Git issues teams face in day-to-day DevOps work 👇 🚫 Merge Conflicts — when multiple people change the same file or line. 💥 Detached HEAD State — happens when you checkout a commit instead of a branch. 🔁 Rebase gone wrong — leads to overwritten commits or lost changes. 🕵️ Wrong branch commits — pushing code to main instead of your feature branch. 🔒 Permission errors — while pushing or pulling due to access or SSH key issues. ✅ Tip: Always take a backup branch before doing a rebase or reset, and pull the latest changes before committing. Git is powerful — mastering it saves hours in debugging and helps maintain clean version control in any DevOps pipeline. #Git #GitHub #DevOps #VersionControl #CICD
To view or add a comment, sign in
-
🚀 𝟵𝟬% 𝗣𝗲𝗼𝗽𝗹𝗲 𝗗𝗼𝗻’𝘁 𝗧𝗿𝘂𝗹𝘆 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗚𝗶𝘁 — 𝗘𝘃𝗲𝗻 𝗔𝗳𝘁𝗲𝗿 𝗨𝘀𝗶𝗻𝗴 𝗜𝘁 𝗗𝗮𝗶𝗹𝘆 🚀 Most DevOps engineers think they know Git… until they face their first merge conflict or rollback disaster. 𝗜𝗻𝘀𝗶𝗱𝗲 𝘁𝗵𝗶𝘀 𝗳𝗿𝗲𝗲 𝗴𝘂𝗶𝗱𝗲, 𝘆𝗼𝘂’𝗹𝗹 𝗹𝗲𝗮𝗿𝗻: 💡 The Fundamentals (But Simplified): → What is Git, how it differs from GitHub, and why it’s the backbone of DevOps ⚙️ Setting Up Git Properly: → Configuring username, email, editor, credentials & verification 🌱 Repository Mastery: → git init, git clone, git add, git commit, git push — explained like never before 🌊 Branching & Merging Done Right: → Creating, switching, and resolving merge conflicts like a pro 🔄 Undoing & Reverting Safely: → reset vs revert vs stash — what to use when 📊 Advanced Git Tips: → git log, aliases, commit graphs & debugging lost commits 🧠 Git Best Practices: → Clean commit messages, safe rebasing, avoiding common disasters #DevOps #Git #GitHub #CICD #Linux #Jenkins #Docker #Kubernetes #Terraform #DevSecOps #DevOpsShack
To view or add a comment, sign in
More from this author
Explore related topics
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development
I started using the gitflow branching strategy on my project once it got more popular, as it allows for great semantic versioning and control.