Skip to content
TheChatArchiveThe Chat Archive
DeepSeekdeepseek-v3-0324· DeepSeekHugging Face LMArena Human Preference 140K

If I want to commit changes to enrich a project github wiki page, but I have not…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Claudeclaude-opus-4-20250514’s answer.
  1. User

    If I want to commit changes to enrich a project github wiki page, but I have not permission(non-contributor), should I create a issue or disscussion?

  2. DeepSeek Assistant

    If you want to contribute to a GitHub project's wiki but don't have write access (i.e., you're not a contributor), the best approach depends on the project's workflow and your intended changes:

    1. Create an Issue (Recommended for most cases)

    • When to use: If your changes are straightforward (e.g., fixing typos, adding small clarifications) or if the wiki is tightly controlled by maintainers.
    • How to do it:
      1. Go to the Issues tab of the repository.
      2. Click New Issue.
      3. Clearly describe the changes you'd like to make (you can even paste the corrected text).
      4. Ask if a maintainer can apply your changes or grant you temporary access.
    • Pros:
      • Issues are more commonly monitored by maintainers.
      • Good for small, actionable improvements.

    2. Start a Discussion (If enabled)

    • When to use: If the project has Discussions enabled and your changes are more substantial (e.g., restructuring, adding new sections) or require community input.
    • How to do it:
      1. Go to the Discussions tab (if available).
      2. Start a new discussion under "Ideas," "Q&A," or "General."
      3. Explain your proposed changes and ask for feedback.
    • Pros:
      • More collaborative; good for gathering opinions before making changes.
      • Less formal than an issue.

    Alternative: Fork the Wiki (If it's a separate repo)

    • Some wikis are stored in a separate repository (e.g., project.wiki.git).
    • If that's the case, you can:
      1. Fork the wiki repo.
      2. Make your changes.
      3. Submit a Pull Request (if allowed) or link your fork in an issue/discussion.

    Which One Should You Choose?

    • Small fixes? → Issue (fastest way to get attention).
    • Big changes or need feedback? → Discussion (if available).
    • Wiki is a separate repo? → Fork + PR (if possible).

    Would you like help drafting a message for the issue/discussion?

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.