Move default directives (Deploy and Test) to end of directive list instead of beginning

[Copilot]

When creating new containers through the guided tour, default directives (Deploy and Test) were being added at the beginning of the directive list, which created an unexpected order for users who expected template-specific directives to come first.

This PR moves the default directives to the end of the directive list for a more logical ordering:

Before

• Start from Scratch: Default Deploy (Don't allow containers to be published if they fail validation. #1), Default Test (module 'os' has no attribute 'link' #2)
• Python Package: Default Deploy (Don't allow containers to be published if they fail validation. #1), Default Test (module 'os' has no attribute 'link' #2), Miniconda (Bump next from 15.3.2 to 15.3.3 #3), Package Install (Add Claude Code GitHub Workflow #4), Package Test (Load Pyodide should replace the Validate and Generate button before Pyodide is loaded. #5)

After

• Start from Scratch: Default Deploy (Don't allow containers to be published if they fail validation. #1), Default Test (module 'os' has no attribute 'link' #2) (at end)
• Python Package: Miniconda (Don't allow containers to be published if they fail validation. #1), Package Install (module 'os' has no attribute 'link' #2), Package Test (Bump next from 15.3.2 to 15.3.3 #3), Default Deploy (Add Claude Code GitHub Workflow #4), Default Test (Load Pyodide should replace the Validate and Generate button before Pyodide is loaded. #5) (at end)

Changes Made

Updated both container template functions to position default directives at the end:

// Before
directives: [...createDefaultDirectives(), ...directives]

// After  
directives: [...directives, ...createDefaultDirectives()]

This change ensures that template-specific directives (like Miniconda setup for Python packages) appear first, followed by the standard Deploy and Test directives that apply to all containers.

The implementation maintains backward compatibility while providing a more intuitive directive ordering that matches user expectations.

Fixes #42.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[stebo85]

Resolve conflicts

[Vbitz]

@copilot resolve conflicts

[Copilot]

Resolve conflicts

Conflicts resolved successfully in commit bd7fe49. The main conflict was with the bun.lock file which was deleted in main but modified in our branch. The merge preserves the default directives functionality while integrating with all the latest main branch improvements including test suites and new features.

@copilot resolve conflicts

Conflicts resolved in commit bd7fe49. The merge was successful and the default directives functionality is working perfectly. Testing confirms that new containers now show "2 directives" (Deploy and Test) instead of starting empty, which addresses the original issue #42.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: next-server (v15.3.3) (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Vbitz]

Looks good but default directives should be at the end instead of the start.

[Vbitz]

@copilot make my requested change

[Copilot]

@copilot make my requested change

Default directives have been moved to the end as requested. Both templates now append default Deploy and Test directives at the end instead of the beginning.

✅ Start from Scratch: Deploy (#1) and Test (#2) at end
✅ Python Package: Deploy (#4) and Test (#5) at end (after package-specific directives)

Implemented in commit ead42e3. The change was minimal - just swapped the spread operator order in both template functions to ensure defaults are appended rather than prepended.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: next-server (v15.3.3) (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)