Fix malformed GitHub Community Organization invitation system

[Copilot]

The GitHub Community Organization invitation system had several critical issues preventing users from successfully requesting membership:

Issues Fixed

1. Malformed YAML Issue Template

The .github/ISSUE_TEMPLATE/invitation.yml file contained severe YAML syntax errors:

• Duplicate keys (type, id, attributes, validations)
• Malformed structure with overlapping field definitions
• Missing YAML document start marker
• CRLF line endings causing parsing failures

Before:

- type: textarea
  id: Additional
  type: input           # Duplicate 'type' key
  id: Email id.         # Duplicate 'id' key  
  attributes:
    label: Email (if applicable)
  validations:
    required: false
  type: textarea        # Another duplicate
  id: Additional        # Another duplicate

After:

- type: input
  id: email
  attributes:
    label: Email (if applicable)
    placeholder: Insert your Email id.
  validations:
    required: false
- type: textarea
  id: additional_context
  attributes:
    label: Additional Context
    description: >
      Where did you meet JD Studio? What do you like about this
      community/Why do you want to join?
  validations:
    required: true

2. Workflow Logic Issues

The .github/workflows/invitation.yml workflow was triggering on ALL labeled events without filtering for the specific invitation label:

Before:

on:
  issues:
    types: [labeled]

jobs:
  automate_invite:
    runs-on: ubuntu-latest
    steps:  # No conditional check - runs for ANY label!

After:

"on":
  issues:
    types: [labeled]

jobs:
  automate_invite:
    runs-on: ubuntu-latest
    if: contains(github.event.label.name, 'invite me to the organisation')
    steps:  # Now only runs for invitation requests

3. Added Documentation and Testing

• Created comprehensive documentation explaining the invitation system
• Added validation testing to prevent future YAML syntax issues
• Improved user experience with better form field organization

Impact

Users can now successfully request to join the GitHub Community Organization using a properly structured form. The automated workflow will correctly process invitation requests only when the appropriate label is applied, preventing false triggers and ensuring reliable operation.

The system now properly handles the complete flow:

1. User fills out structured invitation form
2. Issue is automatically labeled with "invite me to the organisation"
3. Workflow detects the specific label and sends GitHub organization invitation
4. User receives invitation and issue is automatically closed with success message

Fixes #403.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

@VasudevJaiswal 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.