Skip to content

Enable Zenodo-OSF Auto-SyncΒ #7

@daniel-Steger

Description

@daniel-Steger

πŸš€ Pull Request Title

πŸ“Œ Related Issue(s)

Closes #ISSUE_NUMBER
Related to #ISSUE_NUMBER

πŸ“– Summary of Changes

  • πŸ”§ What was changed?
  • πŸ›  Why was it changed?
  • βœ… How does it improve the OSF integration or user experience?

πŸ—‚ Project Context

  • 🎯 Project Name: (e.g., Zenodo-OSF Data Sync, JupyterHub Integration, ORCID Enhancements)
  • πŸ“Œ Feature or Bug Fix Scope: (Small enhancement, major feature, UI improvement, API update, etc.)
  • πŸ›  Part of Iteration/Milestone: (e.g., Sprint #, Phase 1 of feature rollout, etc.)
  • πŸ”— Does this PR connect to other OSF components or APIs? (If applicable, mention affected endpoints or integrations.)

πŸ“ Implementation Details

  • Added/fixed/enhanced [specific functionality]
  • Refactored [code section] for better maintainability
  • Introduced [new method/class] to improve performance

πŸ›  Testing Instructions

  1. Go to [feature page or relevant section].
  2. Perform [specific action].
  3. Verify [expected outcome].

βœ… Checklist

  • My code follows the project's coding style and guidelines.
  • I have added tests that prove my fix is effective.
  • I have added necessary documentation (comments, README, wiki).
  • My changes do not break existing functionality.
  • I have run linting and formatting tools.

πŸ”— Screenshots / GIFs (if applicable)

πŸ“’ Additional Comments


πŸ’‘ Contributor Acknowledgment

πŸŽ‰ Thank you for your contribution! Every PR helps improve OSF’s ecosystem. Your work here supports open science and collaborative research! πŸš€


Why This Works for OSF Open Source Projects

  • πŸ”— Project Awareness: Contributors see how their PR fits into the bigger picture (Project, Milestone, Iteration).
  • πŸ“‹ Structured Process: Encourages best practices with issue linking, testing, and documentation.
  • πŸ›  Developer-Friendly: Clear instructions for maintainers and reviewers.
  • πŸŽ‰ Encourages Participation: Ends with a positive acknowledgment to make contributors feel valued.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions