Expanding on the existing answer:
If your code depends on data, include the schema or an illustrative example of that data. For example use the newly supported tables to explain stuff:
And the number of rows
Or in the case you have ">100 images" that are all similar then embed some illustrative ones in the post to give an idea what you're working with. Obviously if it's just resources like icons or form backgrounds, then I wouldn't consider that data in the same way.
The aim is that your code can be reviewed on the site without clicking on any links, but if you need to execute the code then a link to a working demo on e.g. GitHub would be fine in addition. This extra effort benefits you, as if your post contains all the necessary context for review then you will get more answers. Cautious potential reviewers may be put off having to click external links, or may be on mobile unable to run your code anyway.
This often happens in the Excel and VBA tags where the code is dealing with a workbook. For me the ideal post would:
- include all source code
- include markdown tables to describe your data, or if it is not tabular then screenshots and descriptions
- embed any other images etc that constitute examples of data
- screenshot of the workbook before and after code runs since often formatting in the spreadsheet improves readability
- link to a GitHub repo containing all exported code, and data files and a demo.xlam file with everything conveniently packaged
Now I can review the post on mobile or a work computer without leaving the site, or if it's very complex then download the demo at home and play around with that to figure out how it fits together.