Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
Node-TILify
"Today I Learned" tool that converts text file or a directory of text files to HTML files and beyond
In this week's focus on enhancing the development process for Learn2Blog, I delved into the realm of Continuous Integration (CI) by implementing a GitHub Actions Workflow. Continuous Integration pipelines and workflows are pivotal in modern software development, providing automated checks and balances to ensure code quality and stability.
To start, I turned to the starter-workflows repository, a valuable resource housing diverse YAML files for various project types. My project being in .NET, I checked out the dotnet.yml file to get insights into the setup process. Understanding the YAML syntax and keywords like on, push, jobs, and steps is crucial for crafting an effective workflow. In my case, I wanted to the workflow to trigger "on" any "pushes" on the main branch. The job describes the specific task which can be given a name, and steps outline the necessary steps to run the job.
Drawing inspiration from another open-source project, explore-cli, I learned how to tailor the workflow to accommodate the nested structure of my tester project. This involved specifying the path to the test .csproj file, a key adjustment for successful execution.
Beyond my project, I also contributed to Node-TILify, a similar project by my friend @sdthaker. Although I have an aversion to JavaScript [cue laugh emoji], he threw me a challenge my way. Testing his workflow seemed like a good gig!