Project Description

For a long time, I have been planning to learn more about how OBS is integrating with "SCMs" (Source Code Management systems - for me, that means primarily git, GitLab, and GitHub). For Hack Week 22, I decided to bootstrap a trivial software project on GitHub, with automated builds in OBS, and document the steps as I go along.

Goal for this Hackweek

The first goal is to gain a complete, "A through Z" understanding of the process of integrating a software project in GitHub with OBS, including fully automated builds in OBS on every code change in mainline and implementing a semi-automated release workflow, with a real-life versioning scheme.

The second goal, perhaps more important than the first, is to completely document this "A through Z" understanding by describing in detail the exact steps that need to be taken to achieve the first goal, starting from a "blank slate".

That way, the documentation will be there for me to refer to the next time I need to do this, and it will also be there for others who are interested.

Resources

https://github.com/smithfarm/obsscmdemo

Looking for hackers with the skills:

git github obs obs_scm integration documentation

This project is part of:

Hack Week 22

Activity

  • over 2 years ago: smithfarm added keyword "documentation" to this project.
  • over 2 years ago: smithfarm added keyword "git" to this project.
  • over 2 years ago: smithfarm added keyword "github" to this project.
  • over 2 years ago: smithfarm added keyword "obs" to this project.
  • over 2 years ago: smithfarm added keyword "obs_scm" to this project.
  • over 2 years ago: smithfarm added keyword "integration" to this project.
  • over 2 years ago: smithfarm started this project.
  • over 2 years ago: smithfarm originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    Advent of Code: The Diaries by amanzini

    Description

    It was the Night Before Compile Time ...

    Hackweek 25 (December 1-5) perfectly coincides with the first five days of Advent of Code 2025. This project will leverage this overlap to participate in the event in real-time.

    To add a layer of challenge and exploration (in the true spirit of Hackweek), the puzzles will be solved using a non-mainstream, modern language like D, Crystal, Gleam or Zig.

    The primary project intent is not just simply to solve the puzzles, but to exercise result sharing and documentation. I'd create a public-facing repository documenting the process. This involves treating each day's puzzle as a mini-project: solving it, then documenting the solution with detailed write-ups, analysis of the language's performance and ergonomics, and visualizations.

                                   |
                                 \ ' /
                               -- (*) --
                                  >*<
                                 >0<@<
                                >>>@<<*
                               >@>*<0<<<
                              >*>>@<<<@<<
                             >@>>0<<<*<<@<
                            >*>>0<<@<<<@<<<
                           >@>>*<<@<>*<<0<*<
             \*/          >0>>*<<@<>0><<*<@<<
         ___\\U//___     >*>>@><0<<*>>@><*<0<<
         |\\ | | \\|    >@>>0<*<0>>@<<0<<<*<@<<
         | \\| | _(UU)_ >((*))_>0><*<0><@<<<0<*<
         |\ \| || / //||.*.*.*.|>>@<<*<<@>><0<<<
         |\\_|_|&&_// ||*.*.*.*|_\\db//_
         """"|'.'.'.|~~|.*.*.*|     ____|_
             |'.'.'.|   ^^^^^^|____|>>>>>>|
             ~~~~~~~~         '""""`------'
    ------------------------------------------------
    This ASCII pic can be found at
    https://asciiart.website/art/1831
    
    

    Goals

    Code, Docs, and Memes: An AoC Story

    • Have fun!

    • Involve more people, play together

    • Solve Days 1-5: Successfully solve both parts of the Advent of Code 2025 puzzles for Days 1-5 using the chosen non-mainstream language.

    • Daily Documentation & Language Review: Publish a detailed write-up for each day. This documentation will include the solution analysis, the chosen algorithm, and specific commentary on the language's ergonomics, performance, and standard library for the given task.