Prevent scheduling clashes

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
backend

Research direction

The issue names no files, tests, or entry points and only asks whether scheduling clashes should be checked. Start by locating the app's photo-scheduling flow and determine the expected behavior when a photo is already scheduled for a day. The work is not ready to call done until that behavior is agreed and its scope is defined.

Written by the indexing model from the issue text.

Description

enhancement

Should the app check for scheduling clashes? For example, a photo has already been scheduled for that day

Dominant language
PHP
Stars
24
Forks
6
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/Postbot

All issues in Automattic/Postbot

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.