We need to set up a CI/CD pipeline to automate the building, testing, and publishing of the InstagramClient package. This pipeline should include checks to ensure code quality and successful builds before publishing the package to NuGet.

1. Create a GitHub Actions workflow file to automate the build and test process.
2. Add steps to the workflow to build the project and run unit tests.
3. Add a step to publish the package to NuGet if all checks pass.
4. Ensure the workflow includes triggers for pull requests and pushes to the main branch.
5. Securely store the NuGet API key in GitHub Secrets.

✅
• A GitHub Actions workflow is created and placed in the .github/workflows directory.
• The workflow builds the project and runs unit tests.
• The workflow publishes the package to NuGet upon successful checks.
• The workflow is triggered on pull requests and pushes to the main branch.
• The NuGet API key is securely stored and used in the workflow.

Workflow File (Not Final):

name: CI/CD Pipeline

on:
  push:
    branches:
      - main
  pull_request:
    branches:
      - main

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Setup .NET
        uses: actions/setup-dotnet@v2
        with:
          dotnet-version: '6.0.x'

      - name: Install dependencies
        run: dotnet restore

      - name: Build
        run: dotnet build --configuration Release --no-restore

      - name: Run tests
        run: dotnet test --no-restore --verbosity normal

  publish:
    needs: build
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main'

    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Setup .NET
        uses: actions/setup-dotnet@v2
        with:
          dotnet-version: '6.0.x'

      - name: Install dependencies
        run: dotnet restore

      - name: Build
        run: dotnet build --configuration Release --no-restore

      - name: Pack
        run: dotnet pack --configuration Release --no-restore

      - name: Publish to NuGet
        env:
          NUGET_API_KEY: ${{ secrets.NUGET_API_KEY }}
        run: dotnet nuget push bin/Release/*.nupkg --source https://api.nuget.org/v3/index.json --api-key $NUGET_API_KEY

To improve code readability and maintainability, we need to replace the use of JsonElement with strongly-typed models for the API responses. This will involve creating new model classes that represent the data structures returned by the Instagram API and updating the methods in Instagram to use these models.

1. Identify API Response Structures:
   • Review the Instagram API documentation to identify the structure of the responses for the endpoints used in InstagramClient.
2. Create Model Classes:
   • Create model classes for the following API responses:
   • Access Token Response
   • User Profile
   • User Media
   • Media
   • Media Children
3. Update Methods in Instagram:
   • Update the methods in Instagram to deserialize responses into the new model classes instead of using JsonElement.

✅
• Model classes are created for all relevant API responses.
• Methods in InstagramClient are updated to use the new model classes.
• Unit tests are updated or created to verify correct deserialization of API responses.
• The codebase no longer uses JsonElement for API responses.

We need to publish the Instagram package to NuGet to make it available for public use. This involves several steps, including ensuring all necessary files are in place and configuring the package metadata.

1. Ensure the README.md and LICENSE files are in the root directory of the project.
2. Update the .nuspec file to include the readme and license references.
3. Build the project in Release mode to generate the DLL.
4. Create the NuGet package using nuget pack.
5. Publish the package to NuGet using nuget push.

✅ The package is successfully built and published to NuGet.